New answers tagged

2

You should consider the idea that specifications change. Today there are 50 default fields, tomorrow there could be 51. You do not want to be adding a column every time the requirements change. The reverse might also be true; what if a column is no longer mandatory or is no longer required? The sample ERD below allows the following: people can take a ...


0

I would go for option 1., but I think there is no reason for: a json string which defines the custom fields. Some databases ( eg. PostgreSQL ) have support for traversing JSON, so to get list of keys from a JSON you make: select key from json_each('{"a":"foo", "b":"bar"}'); So in your example you can just select that JSON from answers table ( via ...



Top 50 recent answers are included