From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)topsystem(dot)de> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL Hacker) |
Subject: | Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes |
Date: | 1998-04-29 14:35:26 |
Message-ID: | 8629.893860526@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Meskes <meskes(at)topsystem(dot)de> writes:
> Does this mean I can read in a complete C array with one call? I mean
> something like this:
> char emp_name[10][10];
> exec sql select name into :emp_name from emp;
As far as I know that works now; or at least, if it doesn't work it's
a limitation of the embedded-SQL interface, and not anything that has
to do with libpq or the fe/be protocol.
A "result" in libpq's terms is the result of a single SQL command.
The result of a successful query, for example, is typically multiple
rows of data. You only need a PQgetResult loop if (a) you send a
query string that contains several commands, or (b) you issue a
query whose answer contains more than one kind of tuple.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-04-29 14:50:28 | Re: [HACKERS] Re: [INTERFACES] Revised proposal for libpq and FE/BE protocol changes |
Previous Message | Tom Lane | 1998-04-29 14:28:14 | Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes |