One thing I'd be worried about is that after an add_entity there is no
way to set options on the main entity afterwards. You could provide a
reset_entitypoint, but it wouldn't work the same as with joins because
after a reset_joinpoint you can rejoin along the same path to filter
more criterion if necessary. Still, I think some functionality is
better than no functionality... it's not that big of a deal, is it?
On Dec 8, 8:23 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2007, at 7:25 PM, Chris M wrote:
>
>
>
> > options() could work like joinpoints do - after an add_entity,
> > options() refers to that entity.
>
> probably. ive been hesitant to make things go off of add_entity() as
> of yet.....though actually this is probably not very hard to do. youd
> have to add the option as undefer('large_col'), and i bet if you were
> to change line 542 of interfaces.py to:
>
> if query._entities:
> mapper = query._entities[-1][0]
> else:
> mapper = query.mapper
>
> it *might* work with just that change.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
