From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Missing feature in plpgsql EXECUTE ... USING support |
Date: | 2009-11-13 20:30:33 |
Message-ID: | 162867790911131230j7fc8ade7s7f124fe732e7c606@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/11/13 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> I just noticed that plpgsql's OPEN cursor FOR EXECUTE command lacks
> a USING clause, so the only way to put parameters into the string is
> textual insertion. Seems like an oversight, since every other variant
> of EXECUTE in plpgsql can do USING. Did we omit that intentionally?
>
It's my mistake. I am sure, so OPEN FOR EXECUTE needs USING clause.
It's a paradox so Oracle OPEN function missing any support for dynamic
query. We are better than Oracle :).
Pavel
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Grzegorz Jaskiewicz | 2009-11-13 20:37:41 | Re: cvs head doesn't pass make check on one of the machines here |
Previous Message | Heikki Linnakangas | 2009-11-13 20:19:38 | Hot standby, overflowed snapshots, testing |