| From: | "Clark C(dot) Evans" <cce(at)clarkevans(dot)com> |
|---|---|
| To: | "Marko Tiikkaja" <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David Fetter" <david(at)fetter(dot)org>, "Yeb Havinga" <yebhavinga(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: wCTE behaviour |
| Date: | 2010-11-13 15:36:21 |
| Message-ID: | 1289662581.18786.1405112777@webmail.messagingengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 13 Nov 2010 17:23 +0200, "Marko Tiikkaja" wrote:
> So these queries would behave differently?
>
> WITH t AS (DELETE FROM foo RETURNING *)
> SELECT 1 WHERE false;
>
> WITH t AS (DELETE FROM foo RETURNING *)
> SELECT 1 FROM t LIMIT 0;
I'm still trying to wrap my head around this
new mechanism. What would this return?
UPDATE foo SET access = 0;
WITH t AS (UPDATE foo SET access = access + 1 RETURNING *)
SELECT x.access, y.access
FROM t CROSS JOIN t;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2010-11-13 15:42:25 | Re: wCTE behaviour |
| Previous Message | Marko Tiikkaja | 2010-11-13 15:23:34 | Re: wCTE behaviour |