Brian Troxell <trox@mindspring.com> writes:
> I'm getting an error when forming SELECT statements using the new 7.1
> EXECUTE command. The error states, simply, that there was an unexpected
> SELECT within the EXECUTE command.
For no good reason that I can see, the original coding for EXECUTE
rejected SELECTs. While there isn't a provision for doing anything
with the value(s) returned by the SELECT, this is still pretty silly:
for example "SELECT setval('seq', n)" is useful even without looking
at the result value. So I took out that restriction a day or two ago.
As of the current snapshot, you can execute a SELECT, but the results
will be discarded (unless you do SELECT INTO).
regards, tom lane
