Hrm - maybe I should just quote my actual code rather than the example.
Actually, technically, no - the "hobbies" are NOT shared between people.
So two people can't share the same hobby.
Each Person has their own list of hobbies, and one of those is their
"favorite" and I dont want to have some "favorite" boolean. My actual
code has nothing to do with people and hobbies, this was just a (poor)
I’m new so I don’t have the full answer, but without the favorite boolean, behind the scenes I think a table of “HobbyFavorite” would be needed that has person_id and hobby_id, unless I’m missing something.
So it sounds like you need two “has_one” relationships defined?
both Person and Hobby would have:
You then could have a FavoriteHobby model object with
I’m not 100% this would work or is a good idea, but nobody else has suggested anything yet, so I’m trying to learn in the process. Take any of the above with a HUGE chunk of salt:)
I'm new so I don't have the full answer, but without the favorite
behind the scenes I think a table of "HobbyFavorite" would be needed
has person_id and hobby_id, unless I'm missing something.
Since there would be a 1:1 association between Person and HobbyFavorite,
that would actually be functionally equivalent to just having a
hobby_favorite_id in Person.
That is exactly how the database looks. Instead of people and hobbies,
my code actually uses Users and Characters. The People/Hobby was just
another example. Each user can have any number of characters, but only
one character is marked as the "selected character".
The users table has a selected_character_id, and the characters table
has a user_id.