Hi Michael, I read http://www.sqlalchemy.org/trac/ticket/1751 with some curiousity.
My take on declarative mixins was that _as_declarative should basically accumulate everything from the bases as if it were in the class itself and then let _as_declarative behave exactly as it usually did on the resultant attributes.
As such, I can't see why relationships or foreign keys in columns are a bad thing. You can have multiple classes with a relationship to a single other class, so why not allow that relationship to be abstracted out in a mixin? (DRY and all that...)
cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.