Relational Database Modeling for one off content or configurations
Unanswered
Gazami crab posted this in #help-forum
Gazami crabOP
I know this is not NextJS specific, but couldn't find much after googling, but does anyone have recommendations on how to model the schema for configurations or content that are just for one entity?
For example I have a widget which is unique, and I want to configure it's content, I found the simplest is to create a table with just one row and as many columns as configurable values/content for the widget.
My problem is that this table will only have one row and sounds a bit weird. Is this the correct approach?
For example I have a widget which is unique, and I want to configure it's content, I found the simplest is to create a table with just one row and as many columns as configurable values/content for the widget.
My problem is that this table will only have one row and sounds a bit weird. Is this the correct approach?