Re: Incremental results from libpq
От | Tom Lane |
---|---|
Тема | Re: Incremental results from libpq |
Дата | |
Msg-id | 19391.1131571328@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Incremental results from libpq (Scott Lamb <slamb@slamb.org>) |
Ответы |
Re: Incremental results from libpq
Re: Incremental results from libpq |
Список | pgsql-interfaces |
Scott Lamb <slamb@slamb.org> writes: > Is there a better way? Not at the moment. It's been requested before though, so if you want to develop a patch for libpq, have at it. The main reason why libpq does what it does is that this way we do not have to expose in the API the notion of a command that fails part way through. If you support partial result fetching then you'll have to deal with the idea that a SELECT could fail after you've already returned some rows to the client. I am not sure that this is a huge deal, but it definitely uglifies the API a bit. It would be a good idea to think through exactly what clients will need to do to cope with that fact before you start designing the API extension. regards, tom lane
В списке pgsql-interfaces по дате отправления: