4 ms·
Multiple tables are the way to go with SQL, you'll need multiple tables all over the place. So if multiple tables give you a “wrong” feeling, I argue that the
by hibbelig 4y ago
Multiple tables are the way to go with SQL, you'll need multiple tables all over the place. So if multiple tables give you a “wrong” feeling, I argue that the feeling is wrong for the technology.
It would be very normal to have tables as follows:
* Table "users" with an "id" column and some additional data about the user.
* Table "skills" with an "id" column and some additional data about the skill.
* Table "user_skill" with columns "user_id" and "skill_id" (and the corresponding foreign key constraints).
- never_inline 4y agoI have also done this many times but I think GP has a point. This model needs more code, and a hassle when you're just trying to get something working.
- quickthrower2 4y agoIts a wetware thing. Use relational enough and this isn’t a hassle at all. Like static types are not a hassle if you are used to them. Or docker once used to it. Etc.
- marcosdumay 4y ago> This model needs more code That's not my conclusion at all. This model often requires less code. And less hard-coded data your application has to share around.