On Feb 4, 11:03 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008, at 3:46 PM, Utku Altinkaya wrote:
>
>
>
> > I get it, the result with joins for eager loading has nothing to do
> > with sorting. So I have to join them to base selected set to use. But
> > I feel like selecting twice, is there a peformance penalty here?
>
> > properties =
> > properties
> > .select_from
> > (data
> > .properties_table
> > .join(data.addresses_table.join(data.districts_table)))
>
> yeah if you are joining there, and also joining for the eager load, it
> doesnt perform as well. so consider using order_by=None on the parent
> mapper or query.order_by(None).
Thanks for help and patience, I'm really starting believe you are not
a single person but a huge organization under the name of Michael
Bayer :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
