Hi Florent, On Oct 11, 1:01 pm, "Florent Aide" <[EMAIL PROTECTED]> wrote: > On 10/11/07, James Brady <[EMAIL PROTECTED]> wrote: > > > > Did you call assign_mapper on Ownership? > > [...] > > > However, I'm using the identity framework (part of TurboGears) which > > unfortunately doesn't play nicely with assign_mapper... shame! > > If you use SA 0.3.10 I would advise you to use mapper (from > sqlalchemy.orm import mapper) instead of assign_mapper. > If you could send a post in the TurboGears mailing list about why > identity does not play nice with assign_mapper we would surely find a > solution to your issue :)
So, using mapper rather than assign_mapper brings me back to my original problem of not being able to use the relations I've set up in my models - the ResultProxy object only has the basic keys from the table definition. > I used a lot of assign_mapper myself with TG a few months back, I now > switched to mapper in order to become 0.4 compliant, but I can tell > you TG 1.0.2/1.0.3.x are assign_mapper friendly... 1.0.4beta1 should > also be usable with assign_mapper. So is assign_mapper deprecated in SA 0.4? Is sqlalchemy.orm.mapper the direction I should be heading in? Thanks, James --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
