Hello.
Here is the fully self-contained regression of the issue, including the
workaround for SA 0.7.9. Thank you again, because I wouldn't figure it out
without your help (the select_from part). I haven't tried it on SA 0.9.
If you have any questions, please ask.
HTH,
Ladislav Lenart
On
Hello.
I ended up with the following query:
@classmethod
def _find_contacts_fetch_window(cls, contact_cls, win):
Special data-fetching query for contacts and all their related info
including tags, partner, client,...
NOTE: We build the FROM part entirely by hand,
Hello.
I ended up with the following query:
@classmethod
def _find_contacts_fetch_window(cls, contact_cls, win):
Special data-fetching query for contacts and all their related info
including tags, partner, client,...
NOTE: We build the FROM part entirely by hand,
Hello.
On 13.6.2013 18:44, Michael Bayer wrote:
On Jun 13, 2013, at 11:03 AM, Ladislav Lenart lenart...@volny.cz wrote:
Unfortunately migrating to SA 0.9 is not an option for me at the moment due
to
severe time constraints.
I was pretty sure you'd say that, though I'm really looking
Hello.
I have a query that does a full scan of an inherited table with more than
million rows even though I need only 100 of them (on postgres 9.1). This is a
real bummer! Please help me rewrite the SA query or instruct postgres to not do
this stupidity.
I have the following setup (only the
Please try out 0.9 from the git master which fixes the issue of the nested
SELECT on the right side of a join.
Sent from my iPhone
On Jun 13, 2013, at 9:18 AM, Ladislav Lenart lenart...@volny.cz wrote:
Hello.
I have a query that does a full scan of an inherited table with more than
Unfortunately migrating to SA 0.9 is not an option for me at the moment due to
severe time constraints.
Could you please help me write SA query for 0.7.9 that uses index scan and also
loads all the necessary relations? It must be possible with a proper use of
from_statement(), contains_eager()
Hello.
Just a minor correction:
The new query can return whatever it pleases as long as it *also*
returns Foo instances with properly populated relations.
The rest of the e-mail is the same.
Please help me,
Ladislav Lenart
On 13.6.2013 17:03, Ladislav Lenart wrote:
Unfortunately
On Jun 13, 2013, at 11:03 AM, Ladislav Lenart lenart...@volny.cz wrote:
Unfortunately migrating to SA 0.9 is not an option for me at the moment due to
severe time constraints.
I was pretty sure you'd say that, though I'm really looking to verify that my
fixes are going to hold up under real