| From: | Jeff Shanab <jshanab(at)smartwire(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Libpq enhancement |
| Date: | 2011-06-19 15:04:33 |
| Message-ID: | 615FD77639372542BF647F5EBAA2DBC20B11C251@IL-BOL-EXCH01.smartwire.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am wondering If I am missing something obvious. If not, I have a suggestion for plpgsql.
Stored procedures can accept rows.
Libpq can receive rows (PQResult).
Wouldn't it be a great interface if PQResult was "bi-directional"? Create a result set on the client then call the database with a command.
Perhaps...
PQinsert(PQResult,"schema.table"); //iterate thru rows inserting
PQupdate(PQResult,"schema.table"); //iterate thru rows updateing
PQexec(connection,"scheme.function",PQResult) //iterate thru rows passing row as arg to stored procedure.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-19 15:10:57 | Re: SSI tuning points |
| Previous Message | Cédric Villemain | 2011-06-19 14:44:28 | Re: the big picture for index-only scans |