In the current H2 sizes of JSON and GEOMETRY objects are limited to 1,048,576 bytes. Sometimes it isn't enough (orbisgis/h2gis#1179).
Hypothetically we can make this limit configurable, but from my point of view all really large objects must be off-heap on the server side (excluding possible usage in user-defined functions, we can't control them). It means they should be stored in the same way as LOBs.
There are two possible approaches. We can allocate a couple of new data types (JSON LARGE OBJECT and GEOMETRY LARGE OBJECT) or can add some storage specifiers (similar to FORMAT JSON) to existing CHARACTER LARGE OBJECT and BINARY LARGE OBJECT data types. I think new data types are less intrusive. We also can convert these data types to LOB data types, but with large in-place limit.
@grandinj
@ebocher
In the current H2 sizes of
JSONandGEOMETRYobjects are limited to 1,048,576 bytes. Sometimes it isn't enough (orbisgis/h2gis#1179).Hypothetically we can make this limit configurable, but from my point of view all really large objects must be off-heap on the server side (excluding possible usage in user-defined functions, we can't control them). It means they should be stored in the same way as LOBs.
There are two possible approaches. We can allocate a couple of new data types (
JSON LARGE OBJECTandGEOMETRY LARGE OBJECT) or can add some storage specifiers (similar toFORMAT JSON) to existingCHARACTER LARGE OBJECTandBINARY LARGE OBJECTdata types. I think new data types are less intrusive. We also can convert these data types to LOB data types, but with large in-place limit.@grandinj
@ebocher