0

Is it OK to sometimes instead of making a join table for a many-to-many relation, store the ids of entity A in a column of entity B? It would look something like this:

// A
id | name
---------
10 | foo
20 | bar

// B id | name | AIds


30 | buzz | 10,20

I only need to know which A's are owned by B when looking at B, and not the other way around (and I can handle the logic in code, joins are not necessary). Hence the lack of a join table.

Or are there some bad aspects to this I'm not seeing?

0 Answers0