From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | kogorman(at)pacbell(dot)net |
Cc: | PGSQL Hackers List <pgsql-hackers(at)hub(dot)org> |
Subject: | Re: Rule system goes weird with SELECT queries |
Date: | 2000-10-20 00:10:11 |
Message-ID: | 12897.972000611@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin O'Gorman" <kogorman(at)pacbell(dot)net> writes:
> When I actually *execute* the 'insert into dummy', I get the output of
> only one select: the second one listed. Is there something about
> executing a list I don't know about, or is this also old news??
If you're using psql then that doesn't surprise me, because psql submits
queries via PQexec, and PQexec is not capable of dealing with multiple
result sets per submitted query string --- its API provides no way to
handle that, so it just bit-buckets all but the last command result.
This would work OK in an app that uses PQsendQuery followed by a
PQgetResult loop, however. See
http://www.postgresql.org/devel-corner/docs/postgres/libpq-async.htm
I've been kind of wanting to update psql to use these lower-level
routines, but that item has been languishing in the to-do queue for
a couple years now...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin O'Gorman | 2000-10-20 00:52:30 | Proposed relaxation of CREATE RULE syntax |
Previous Message | Hiroshi Inoue | 2000-10-19 23:52:14 | Re: time stops within transaction |