On Nov 23, 2007, at 6:11 AM, Pierre-Yves Strub wrote:
> > Hi again, > > Now using SQLAlchemy r3811, using the code at > http://pastie.caboo.se/121148 > > In this case, the merge operation do some lazy loading. When > no inheritance is in use, the behaviour is not visible since the lazy > loaded instance are already merged in the session (but the log output > clearly states that some lazy loading is done (1)). When using > inheritance, child tables are queried for each lazy loaded attribute. > > Thanks again, Pierre-yves. > OK since we have the new restriction of merge/dont_load instances being "clean", i was able to ratchet down the copy operation to also not fire off any events, since its ultimately backrefs firing off that led to the lazy loads. some extra tests added in r3812. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
