On Dec 15, 2007, at 9:34 AM, Vladimir Iliev wrote:
> hi, i hit another dynamic relations related bug. if you remove > lazy='dynamic' from items mapping there's no problem. > OK, I know what this is and it involves making query translation a little more intelligent. The issue is not really the "dynamic", its the eager loads in conjunction with the limit/offset (and the fact that youre joining a select of two tables to one of the sub tables), and its not able to alias properly when it makes its subqueries since its traversing too deeply and breaking up your inner query. ill have this fixed by tomorrow...its ticket #904. As a workaround for now, either turn off the eager loads in the mapper() configurations and just use eagerload() as an option as needed; or use all() on the dynamic relation (which sort of defeats the purpose of a dynamic relation....) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
