You should do what is most performant not what is "easiest to read".
Your context hasn't been stated – but in general for databases optimize for the machine, not the human. That's what OO is for.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi @brokenthorn , thanks for the comment!
It's a trade-off between "JOIN" and "Let the table grow as the number of value objects grows".
In this case, I think those depend on the context.
Remember tables are for computers not humans.
You should do what is most performant not what is "easiest to read".
Your context hasn't been stated – but in general for databases optimize for the machine, not the human. That's what OO is for.