On Sun, 3 Aug 2014, nathan wrote:
Yes, you have it exactly right. There's currently 1 song to 1 player, but I'm thinking of going ahead and experimenting with assigning more than 1 song to a player.
Nathan, It does not matter if you know the relationship(s) you want you can define them properly. Remember that it's possible for a table to be a child of a parent and the parent to a child table. The 1:1 relationship is fairly straight-forward. With the 1:Many and Many:1 it's a bit more complex, but the backref() helps once that's understood. The tricky part is making sure you understand which table is the 1 and which table is the Many. It's easy to get them backwards. Regards, Rich -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
