-Original Message-
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com]
On Behalf Of Michael Bayer
Sent: 27 September 2011 19:37
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] Possible bug with subqueryload
On Sep 27, 2011, at 1:16 PM, King Simon
that mapper.order_by thing is fixed in 0.7.3/0.6.9 tip.
--
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
On Wed, Sep 28, 2011 at 2:15 PM, Michael Bayer mike...@zzzcomputing.comwrote:
that mapper.order_by thing is fixed in 0.7.3/0.6.9 tip.
Brilliant - thanks again for all the time you put in to SA and this group,
Simon
--
You received this message because you are subscribed to the Google Groups
Hi,
I think there may be a bug in the interaction between 'subqueryload' and
having a default 'order_by' defined on a mapped class. When the subquery
is run, it looks like the ORDER BY is being placed on the outer query,
whereas it should be on the inner query. The full test case is below,
but
Hi Simon -
yeah that looks pretty buglike to me, mapper.order_by is not a frequently used
feature so this one may need some adjustment.
I've created http://www.sqlalchemy.org/trac/ticket/2287 to take a look at this
and so far I'm targeting it at 0.6.9/0.7.3.
On Sep 27, 2011, at 7:29 AM, King
-Original Message-
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com]
On Behalf Of Michael Bayer
Sent: 27 September 2011 16:24
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] Possible bug with subqueryload
Hi Simon -
yeah that looks pretty buglike
On Sep 27, 2011, at 1:16 PM, King Simon-NFHD78 wrote:
Great, thanks a lot :-) I only discovered it in a toy application, and
the workaround (including order_by on the query) is not a problem.
In this toy application, I was also wondering if there existed a
mechanism for doing some sort
