options() could work like joinpoints do - after an add_entity,
options() refers to that entity.
On Dec 8, 7:12 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2007, at 6:17 PM, Chris M wrote:
>
>
>
> > t1, t2 =
> > Table1
> > .options
> > (undefer
> > ("table2.large_col")).join("table2").add_entity(Table2).first()
>
> > does not load "large_col" (or even put it in the SQL sent) on t2. Is
> > undefer meant for eager loading in this scenario only, or have I
> > stumbled upon a bug? (if the former, is there a way to achieve what I
> > was trying to do?)
>
> query options currently only apply to the main entity. in this case
> specfically a new syntax would need to be introduced since its not
> clear if the above option applies to the attribute as applied to the
> Table1.table2.large_col attribute or on the large_col attribute on the
> secondary entity (since the two collections of Table2 could be
> disjoint).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
