Timeline for Saving sets into database fields [duplicate]
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2017 at 8:01 | history | closed |
amon 8bittree gnat Pieter B CommunityBot |
Duplicate of Is storing a list of strings in single database field a bad idea? Why? | |
| Nov 6, 2017 at 23:16 | answer | added | Christophe | timeline score: 3 | |
| Nov 6, 2017 at 18:55 | comment | added | Robert Harvey | You don't have to save the list into a single field. Your example is just a display; you can put the audience in its own table and still have it displayed as a comma delimited list. | |
| Nov 6, 2017 at 15:17 | review | Close votes | |||
| Nov 10, 2017 at 7:49 | |||||
| Nov 6, 2017 at 12:56 | comment | added | Walfrat | Working idea ? yes. Standard ? No, standard are using another table with foreign key and unique constraint (for set only not list), Good ? It depends of the requirments. If you really want to know if it's a good idea, we would need more information : volume of data, what kind of request are performed against the set ? | |
| Nov 6, 2017 at 12:36 | history | asked | Niklas Rosencrantz | CC BY-SA 3.0 |