Menu
Community /Pin to ProfileBookmark
@NogDogJan 11.2021 — #It _might_ be possible to make a join work that way, but I can't see how it could do it efficiently (i.e. leverage table indexes instead of doing full table reads). Personally, I'd just make the little 2-column join table (with a unique index across both columns if no car should ever be assigned to more than one person, otherwise just a regular index).@NogDogJan 11.2021 — #I suppose with the "right" framework that has built in database creation commands, it might just be a fairly simple set of a few commands to create that table and add "has_many" relationships to the other 2 tables. However, "simple" is complicated by the fact that you first have to learn how to do that in that particular framework -- along with everything else you have to learn about it to get it to work. 😐️
Store an array in a single column
I’m needing to store an array in my database. I could do a second table and join ID’s together but it seems like a lot of work.
I have a person table, personID as the index.
I then have a car table with carID as index.
Some people will be assigned multiple cars. In the person tale can I store an array like 47,52,14 and then still join them to the cars table?
Sign in
to post a comment3 Comments(s) ↴
0
@NogDogJan 11.2021 — #It _might_ be possible to make a join work that way, but I can't see how it could do it efficiently (i.e. leverage table indexes instead of doing full table reads). Personally, I'd just make the little 2-column join table (with a unique index across both columns if no car should ever be assigned to more than one person, otherwise just a regular index).0
@NogDogJan 11.2021 — #