Yeah, this is pretty textbook selection bias.
andrew
joined 5 months ago
In this economy I'm going to settle for a used threeskin in the next year or two.
Huuuge... Tracts of land.
The real primary benefit of storing your relationships in a separate place is that it becomes a point of entry for scans or alterations instead of scanning all entries of one of the larger entity types. For example, "how many users have favorited movie X" is a query on one smaller table (and likely much better optimized on modern processor architectures) vs across all favorites of all users. And "movie x2 is deleted so let's remove all references to it" is again a single table to alter.
Another benefit regardless of language is normalization. You can keep your entities distinct, and can operate on only one of either. This matters a lot more the more relationships you have between instances of both entities. You could get away with your json array containing IDs of movies rather than storing the joins separately, but that still loses for efficiency when compared to a third relationship table.
The biggest win for design is normalization. Store entities separately and updates or scans will require significantly less rewriting. And there are degrees of it, each with benefits and trade-offs.
The other related advantage is being able to update data about a given B once, instead of everywhere it occurs as a child in A.
Do hot dogs need genders?
Judging by the stars I'm pretty sure it was night time.
Well, when you're a star, they let you do it. You can do anything.
We got a bill for 5k for a 3 mile ambulance ride and ibuprofen at the ER when my youngest had a febrile seizure.
Is it really that surprising though?
There were 12 of these angry dogs, though. Not one trusting dog in a cinder pit. I don't know if Noem would have been able to handle it even with a gun.