From: | Thomas Markus <t(dot)markus(at)proventis(dot)net> |
---|---|
To: | "W(dot) Matthew Wilson" <matt(at)tplus1(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to tame a gigantic (100+ lines) query in a web app? |
Date: | 2011-08-15 11:50:27 |
Message-ID: | 4E490803.4070605@proventis.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
use WITH queries, I use this regularly and it works fine.
http://www.postgresql.org/docs/9.0/static/queries-with.html
regards
Thomas
Am 14.08.2011 16:39, schrieb W. Matthew Wilson:
> I'm sure I'm not the first person to end up with a gigantic query that
> does lots of left joins and subselects.
>
> It seems to work, but I would love to break it up into smaller chunks.
>
> I'm thinking about rewriting the query to make several temporary
> tables that are dropped on commit, and then joining them at the end.
>
> I can't just use views for everything because I use parameters passed
> in from the web app. I am using a few views where I can.
>
> Is there anything dangerous about making temporary tables in this way?
> I started two transactions simultaneously and they were both able to
> make their own temporary tables.
>
> More generally, how to tame this big ol' query?
>
> The temporary tables mean I'm only pulling data from the database one
> time. ORMs often pull data from one query and then use that data to
> write the next query. This seems slow to me.
>
> Matt
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rebecca Clarke | 2011-08-15 12:10:16 | Pg_dump Query |
Previous Message | Vincent de Phily | 2011-08-15 10:31:49 | altering foreign key without a table scan |