Re: How to tame a gigantic (100+ lines) query in a web app?
| От | Thomas Markus |
|---|---|
| Тема | Re: How to tame a gigantic (100+ lines) query in a web app? |
| Дата | |
| Msg-id | 4E490803.4070605@proventis.net обсуждение исходный текст |
| Ответ на | How to tame a gigantic (100+ lines) query in a web app? ("W. Matthew Wilson" <matt@tplus1.com>) |
| Список | 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 > >
В списке pgsql-general по дате отправления: