Re: Libpq enhancement
От
Dmitriy Igrishin
Тема
Re: Libpq enhancement
Дата
Msg-id
BANLkTinQxO-DX24KBCJgvp4Or-3c-joAvg@mail.gmail.com
Ответ на
Libpq enhancement (Jeff Shanab)
Список
Дерево обсуждения
Libpq enhancement Jeff Shanab <jshanab@smartwire.com>
Re: Libpq enhancement Andrew Chernow <ac@esilo.com>
Re: Libpq enhancement Robert Haas <robertmhaas@gmail.com>
Re: Libpq enhancement Merlin Moncure <mmoncure@gmail.com>
Re: Libpq enhancement Robert Haas <robertmhaas@gmail.com>
Re: Libpq enhancement Dmitriy Igrishin <dmitigr@gmail.com>
Hey Jeff,
--
// Dmitriy.
2011/6/19 Jeff Shanab <jshanab@smartwire.com>
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.
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.
В списке pgsql-hackers по дате отправления
От: Andrew Dunstan
Дата:
