| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: CTEs and re-use |
| Date: | 2017-04-12 02:47:45 |
| Message-ID: | 2B9243AD-09BA-4E0D-9805-5A1E1409F0FA@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> On Apr 11, 2017, at 8:43 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Tuesday, April 11, 2017, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> If ‘on commit drop’ does the trick that clears the annoyance but still wondering if there’s a way to retain the product of the CTE/select for further processing without resorting to a temp table.
>
> A CTE is a same-query-only temp table. If you need it to persist post query you have to use a real temporary table.
>
> David J.
Right then. Thought I might be missing some nifty construct. A little surprised but oh, well.
Thanks for taking the time.
rjs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2017-04-12 03:05:36 | Re: CTEs and re-use |
| Previous Message | David G. Johnston | 2017-04-12 01:47:02 | Re: CTEs and re-use |