Re: PQfformat() and Composite Formatted Results

Поиск
Список
Период
Сортировка
От Volkan YAZICI
Тема Re: PQfformat() and Composite Formatted Results
Дата
Msg-id 20060108203411.GA11875@alamut
обсуждение исходный текст
Ответ на Re: PQfformat() and Composite Formatted Results  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: PQfformat() and Composite Formatted Results  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: PQfformat() and Composite Formatted Results  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-interfaces
Hi,

I've prepared a patch[1] which makes it possible to use composite formats
in query results.

It defines
 PQexecParams() PQexecPrepared() PQsendQueryParams() PQsendPrepared()

functions with last
 int resultFormat

parameter replaced with
 int       nResFormat, const int resParamFormats

Therefore, it breaks compatibility with the existing PQ*Params() and
PQ*Prepared() functions. (Use at your own risk.)

There's also a test case[2] too

[1] http://www.students.itu.edu.tr/~yazicivo/libpq_res_fmt.patch
[2] http://www.students.itu.edu.tr/~yazicivo/pg_res_fmt.c


Any comments will be appreciated.
Regards.


On Dec 30 06:52, Tom Lane wrote:
> It's not a protocol restriction, it's a libpq restriction made in the
> name of keeping the API from getting too unwieldy.  We could add more
> entry points with different parameter lists to address this.  I have
> a feeling that refactoring the API of the query functions entirely
> might be a better idea, though.


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

Предыдущее
От: Ludek Finstrle
Дата:
Сообщение: libpq and auth type
Следующее
От: JiangWei
Дата:
Сообщение: Re: HOWTO pass "default value" to PQexecParams?