On Oct 28, 2011, at 2:28 PM, JPLaverdure wrote: > Hello Michael, > > Sorry to be the thorn in your side.. > I attached a test case as requested.. Ticket 2312.
thanks for the ticket and this is fixed in radadaccc1bb5 . > Also, it seems this is incompatible with history_meta based versioning. > (Which probably has to do with the use of the > function. I can sort of see that, but not quite - in this recipe, all the columns/tables are created as they normally are, not within __declare_last__(), unless I guess you want __history_mapper__ on the abstract base with the same polymorphic setup..... The patch attached to http://www.sqlalchemy.org/trac/ticket/2313 may achieve part of this, but I don't know about the "polymorphic" loader, would that ever have worked with the history_meta system ? I would think history_meta would need special steps to work along with polymorphic selectables. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
