From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matt Miller <mattm(at)epx(dot)com> |
Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL: SELECT INTO EXACT |
Date: | 2005-07-29 21:52:55 |
Message-ID: | 21957.1122673975@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Matt Miller <mattm(at)epx(dot)com> writes:
> This patch implements an optional EXACT keyword after the INTO keyword
> of the PL/pgSQL SELECT INTO command. The motivation is to come closer
> to Oracle's SELECT INTO behavior: when SELECTing INTO scalar targets,
> raise an exception and leave the targets untouched if the query does not
> return exactly one row. This patch does not go so far as to raise an
> exception, but it can simplify porting efforts from PL/SQL.
Uh, what's the point of being only sort-of compatible? Why not throw
the exception?
I dislike the choice of "EXACT", too, as it (a) adds a new reserved word
and (b) doesn't seem to convey quite what is happening anyway. Not sure
about a better word though ... anyone?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-07-29 22:04:52 | Re: PL/pgSQL: SELECT INTO EXACT |
Previous Message | Tom Lane | 2005-07-29 21:46:11 | Re: [HACKERS] Autovacuum loose ends |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-07-29 22:04:52 | Re: PL/pgSQL: SELECT INTO EXACT |
Previous Message | Tom Lane | 2005-07-29 21:46:11 | Re: [HACKERS] Autovacuum loose ends |