Is breaking the atomicity rule justified here?
working one a side project and i came across a problem , i want users to save to their profile their preferred colors, user can have one or multiple preffered colors , the good way to do it is to just have a separate table UserPreferredColors
but im thinking, since its use case will be very limited why waste a whole table for that, maybe just add it to the user table as column where the value is a list,
the colors will not be detailed, there isnt specific hex or names just a standardised list of colors the user can select one or multiple like this screenshot i took from Color Hunt
but im thinking, since its use case will be very limited why waste a whole table for that, maybe just add it to the user table as column where the value is a list,
the colors will not be detailed, there isnt specific hex or names just a standardised list of colors the user can select one or multiple like this screenshot i took from Color Hunt
A friendly place for developers to meet other devs, ask questions, get help, and just have a good time 🙂.
36,263Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
