That's a really simple use case -- you want the primary key to be a 1:1 relationship, and you don't have potentially competing fields.
But this gets complicated when: - You want User.addresses to be a single item ( User.address ) - You don't want User.addresses to just be all the addresses -- but to be filtered on "is_current_address = True" - User has a column name called 'address' or 'addresses'; the join would want to be named "email_addresses" or "postal_address" . It's not that SqlAlchemy can't do this stuff -- it's that it chooses not to, so you have full control of your schema. That's why it's in the extensions, not the core. -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
