Create layout config table in user database #277

Closed
opened 2026-04-14 08:21:52 +00:00 by a24vinla · 4 comments
Collaborator

Since we decided to store layout as raw JSON we need to do some research on how do that.

Since we decided to store layout as raw JSON we need to do some research on how do that.
a24vinla changed title from Create Config table in user database to Create layout config table in user database 2026-04-14 08:22:06 +00:00
a24vinla removed their assignment 2026-04-14 08:22:33 +00:00
Collaborator

researcher on to use json or jsonb .
Conclusion
At first glance, jsonb seems to be the obvious choice. More features and more efficient storage. The problem is that the structure of the json file can be changed. Since we are only interested in storing and retrieving the file, not changing it in the database's json format, it was considered a better choice.

[researcher on to use json or jsonb ](https://www.dbvis.com/thetable/json-vs-jsonb-in-postgresql-a-complete-comparison/). **Conclusion** At first glance, jsonb seems to be the obvious choice. More features and more efficient storage. The problem is that the structure of the json file can be changed. Since we are only interested in storing and retrieving the file, not changing it in the database's json format, it was considered a better choice.
Collaborator

Sorry misclicked

Sorry misclicked
Author
Collaborator

What we want to store is layout-JSON, name and layout order number (it is possible for a user to have multiple layouts and the order number should reflect reflect the ordering of layouts (duh)). It should also have an ID and a foreign key to the User.

What we want to store is layout-JSON, name and layout order number (it is possible for a user to have multiple layouts and the order number should reflect reflect the ordering of layouts (duh)). It should also have an ID and a foreign key to the User.
Collaborator

The tabel has been implemented and merged in #535

The tabel has been implemented and merged in #535
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
Reference
Andras/BoundlessFlowCampus2K#277
No description provided.