On Dec 29, 2008, at 1:53 PM, Alan Shields wrote:
> > My apologies, but I don't see what you're saying. I'm a bit confused > how pool_table in the run2pool_a subquery is being turned into a > subquery as well when there's an eagerload. > I dont either since you've only been sending code fragments along. Your code is too complex for others (well at least me) to understand it in a fragmented style. Please send along a SQL statement which is what you'd like to see for this particular query. Additionally, if you'd like to send along succinct Table definitions with just the relevant columns, I can show you how to render the desired SQL using those table defs. Whether or not eagerload() has the ability to render the desired SQL without you specifying it manually remains to be seen. As I mentioned earlier, you can use the ORM Query object to load objects and eagerly loaded attributes or collections attached to those objects using entirely hand-constructed SQL, as an alternative to using eagerload() to automatically render the LEFT OUTER JOIN. --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
