On 7/29/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Matt Miller <[EMAIL PROTECTED]> 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

just wonder, why that is not the default behavior of the SELECT INTO?
at least, the first time i think the function was right until i found
that the first row of a set of rows was assigned...

i mean, when you do that code you are expecting just one row from your
query, doesn't you?

Jaime Casanova
(DBA: DataBase Aniquilator ;)

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to