On Apr 14, 2008, at 4:46 PM, John Sutherland wrote:
> > 5. We also have a circumstance where we have 2 objects in difference > databases that represent the same thing, but have a slightly different > schema (someone named one field differently), is it possible to have a > single object or table class to represent both? theres a lot of ways to do this kind of thing, the most simplistic is just to have two subclasses of a common class, and map each subclass distinctly - the actual column name can be normalized within the Table or mapper() construct across both classes. We have a feature called "entity_name" that also does this without the subclassing, but I'm trying to determine a use case for entity_name that isn't better accomplished by just using subclasses. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
