Re: PQexecParams with binary resultFormat vs BINARY CURSOR

Поиск
Список
Период
Сортировка
От Dmitriy Igrishin
Тема Re: PQexecParams with binary resultFormat vs BINARY CURSOR
Дата
Msg-id CAAfz9KNW2CtCHOOHcZvq2HUMXsLfjAe=fiaPB=vmjtYYAEXLGA@mail.gmail.com
обсуждение исходный текст
Ответ на PQexecParams with binary resultFormat vs BINARY CURSOR  (Mateusz Łoskot <mateusz@loskot.net>)
Ответы Re: PQexecParams with binary resultFormat vs BINARY CURSOR  (Mateusz Łoskot <mateusz@loskot.net>)
Список pgsql-general
Hey Mateusz,

2011/11/11 Mateusz Łoskot <mateusz@loskot.net>
Hi,

Considering query for binary data stored directly in tables
using libpq API, I'm trying to understand what is the difference
between specifying binary format in functions like
PQexecParams and use of BINARY CURSOR.

For example, with query like this:

SELECT large_image FROM tbl;

where large_image is a custom type,
is there a big difference between binary format specified
to libpq and use of BINARY CURSOR?
Is it client-side binary vs server-side binary processing?

Simply, I'd like to avoid textual<->binary conversions at any stage.

(Endianness is not an issue here.)

Best regards,
"...The concept of a binary cursor as such is thus obsolete when using extended query protocol — any cursor can be treated as either text or binary. ..."
from
http://www.postgresql.org/docs/9.1/static/sql-declare.html

--
// Dmitriy.


В списке pgsql-general по дате отправления:

Предыдущее
От: "Albe Laurenz"
Дата:
Сообщение: Re: strange behavior, hoping for an explanation
Следующее
От: Mateusz Łoskot
Дата:
Сообщение: Re: PQexecParams with binary resultFormat vs BINARY CURSOR