| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Shanab <jshanab(at)smartwire(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Libpq enhancement |
| Date: | 2011-06-20 01:08:34 |
| Message-ID: | BANLkTi=dLGqruAizZvMLZGMUj1s5fi2iJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 19, 2011 at 11:04 AM, Jeff Shanab <jshanab(at)smartwire(dot)com> wrote:
> 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.
For insert, we have something like this already - this is what "copy" is for.
For update, it's a bit more complex - we don't have a "replace into" operator...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-20 01:10:02 | Re: pika buildfarm member failure on isolationCheck tests |
| Previous Message | Robert Haas | 2011-06-20 00:49:19 | Re: [WIP] cache estimates, cache access cost |