Andras/BoundlessFlowCampus2K
4
7
Fork 0
Code Issues 90 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Create layout config table in user database #277

New issue
Closed
opened 2026-04-14 08:21:52 +00:00 by a24vinla · 4 comments
a24vinla commented 2026-04-14 08:21:52 +00:00
Collaborator
Copy link

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
a22erigr commented 2026-04-14 09:28:32 +00:00
Collaborator
Copy link

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.
a22erigr commented 2026-04-19 15:31:58 +00:00
Collaborator
Copy link

Sorry misclicked

Sorry misclicked
👎 1
a24vinla commented 2026-04-23 11:08:21 +00:00
Author
Collaborator
Copy link

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.
a22erigr commented 2026-05-05 08:37:15 +00:00
Collaborator
Copy link

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 Branch/Tag specified
Branches Tags
main
#1236-edit-mode-txt
#1229-generic-themed-buttons
Add-an-option-to-set-no-image-to-image-view-1227
#1242-prog-bar-colors-fix
#1239-Remove-Vertical-Scroll
Image-view-error-1230
Make-the-card-title-and-header-of-card-uniform-1233
both_teams_week_8
team_2_week_7
team_1_week_7
temp_branch_week_7
team_2_week_6
team_1_week_6
team_2_week_5
team_1_week_5
temp_branch_week_5
team_2_week_4
team_1_week_4
week_4_temp_branch
temp-branch-week-3
team_2_week_3
team_1_week_3
team_2_week_2
team_1_week_2
temp-week-2-merge-branch
team_2_week_1
team_1_week_1
No results found.
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked, waiting for further changes

   
bug

Something is not working

  
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
help wanted

Need some help

  
invalid

Something is wrong

  
low priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
script

   
security

use this for security-related issues

  
SQL

  
style

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
a22erigr
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
#273 Create service to enable connection to database
Andras/BoundlessFlowCampus2K
Reference
Andras/BoundlessFlowCampus2K#277
No description provided.