Hello again.
I have successfully installed SA 0.7.10 and the query as-is works. However
jonedload_all / subqueryload_all options on the query do NOT work. I have
slightly extended your cte_example which now demonstrates the issues.
joinedload_all does not crash but there is undesired sql activity
Hello.
I have new insigths / new bug to report.
Even when I reformat the query like this:
q = session.query(Client, PersonalClient, CorporateClient)
q = q.outerjoin(PersonalClient, Client.id == PersonalClient.id)
q = q.outerjoin(CorporateClient, Client.id ==
All of that has been fixed in 0.8. With 0.8 both versions work fine.
On Feb 28, 2013, at 5:29 AM, Ladislav Lenart lenart...@volny.cz wrote:
Hello again.
I have successfully installed SA 0.7.10 and the query as-is works. However
jonedload_all / subqueryload_all options on the query do NOT
Hello again, Michael.
Just a follow-up to my previous post. The following code does not work as I
would like:
q = session.query(Client, PersonalClient)
q = q.join(PersonalClient, Client.id == PersonalClient.id)
if eager:
q = q.options(
Cool!
I will switch to it once it is officially released.
Thank you,
Ladislav Lenart
On 28.2.2013 19:04, Michael Bayer wrote:
All of that has been fixed in 0.8. With 0.8 both versions work fine.
On Feb 28, 2013, at 5:29 AM, Ladislav Lenart lenart...@volny.cz wrote:
Hello again.
I
a join() or a joinedload to a polymorphic selectable always wraps the right
side in a subquery as the ORM doesn't directly support rendering of an
expression like a JOIN (b JOIN c ON b.id=c.id) ON a.id=b.id. The expression
language does, but within the ORM it uses the subquery approach when
