Re: [patch] libpq one-row-at-a-time API
От | Marko Kreen |
---|---|
Тема | Re: [patch] libpq one-row-at-a-time API |
Дата | |
Msg-id | CACMqXCLj__3pdBWHn2hbabVzaWRasTiU2FYYdGnFy_LCV1-KfQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [patch] libpq one-row-at-a-time API (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: [patch] libpq one-row-at-a-time API
|
Список | pgsql-hackers |
On Wed, Jul 25, 2012 at 1:29 AM, Merlin Moncure <mmoncure@gmail.com> wrote: > On Tue, Jul 24, 2012 at 4:59 PM, Marko Kreen <markokr@gmail.com> wrote: >> So if we give only PQgetResult() in 9.2, I do not see that we >> are locked out from any interesting optimizations. > > Well, you are locked out of having PQgetResult reuse the conn's result > since that would then introduce potentially breaking changes to user > code. You can specify special flags to PQsend or have special PQgetResultWeird() calls to get PGresults with unusual behavior. Like I did with PQgetRowData(). I see no reason here to reject PQgetResult() that returns normal PGresult. -- marko
В списке pgsql-hackers по дате отправления: