| From: | Dmitriy Igrishin <dmitigr(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-19 19:36:55 |
| Message-ID: | BANLkTinQxO-DX24KBCJgvp4Or-3c-joAvg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hey Jeff,
2011/6/19 Jeff Shanab <jshanab(at)smartwire(dot)com>
> 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
>
IMO, mapping C functions to SQL operators is bad idea.
If I understood you correctly, you want to make libpq ORM. But
without implementing a functional like C++ virtual functions on
the _backend_ side, it is impossible or ugly.
--
// Dmitriy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-06-19 19:38:28 | Re: Adding a distinct "pattern" type to resolve the "~" commutator stalemate |
| Previous Message | Cédric Villemain | 2011-06-19 19:32:13 | Re: [WIP] cache estimates, cache access cost |