You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently i can not build complex schemas with different denormalizations. Now it is strictly relational. So i suggest you to add custom data types and lists/maps.
The text was updated successfully, but these errors were encountered:
Lists and maps are necessary for non-relational databases.
A simple example of denormalization in relational is to create a list of any type in A to avoid joins. It works well if this list won't be large and is primarily used for read queries. An example could be a "books" table with field "authors" as list of strings .
Also, using JSON schema definitions is a good idea. We can store different JSONs in the "events" table but with clearly defined possible schemas. For example: "type EventCreated," "type EventCanceled," and a table "events" with a "event_data" field of "json[EventCreated, EventCanceled]" type.
Currently i can not build complex schemas with different denormalizations. Now it is strictly relational. So i suggest you to add custom data types and lists/maps.
The text was updated successfully, but these errors were encountered: