Add support JSON data type

tmdoit

Is it in your roadmap?

gabriel

You can already add JSON data and process it inside backend and frontend functions. What use case do you want to address?

tmdoit

Currently I don't have access to Rei3 platform, which data type should I use?

gabriel

You can store JSON blobs in text attributes. You can then read them directly as JSON (variable := attribute_name::JSON) within your backend functions to use regular JSON functions for reading or editing parts of it. The same on the frontend: Send it as text and then parse it as JSON with JSON.parse() in Javascript.

usr338

gabriel What about indexing column that hold json object in database(GIN index) and PostgreSQL JSON-specific query capabilities. ?

gabriel

usr338
Because adding any data type has a long list of consequences and features that must follow for a low-code tool to work. If there is a major benefit or a capability we need, the effort might be worth it.

But I do not know of a use cases that would justify this, which cannot be addressed by existing features. Adding everything into a platform "because its possible" introduces bloat, bugs and more maintenance effort going forward. With limited resources, you can quickly loose all your dev time to supporting features that are not beneficial to the vast amount of users.

usr338

gabriel I completely understand the effort needed and consequences of adding new data type.
As you know, in certain cases where on the relation attribute of type JSON, operations like searches, grouping, joins with other relations are used repeatedly, the performance will be much higher using the JSON data type. In such cases, if REI3 is used, it may be better to design the relations differently. Thank you.