Re: B7 option

Поиск
Список
Период
Сортировка
От Barry Bell
Тема Re: B7 option
Дата
Msg-id 4D51A19E0157604B94159573456A98FA2E7ACE07@BLUPRD0811MB413.namprd08.prod.outlook.com
обсуждение исходный текст
Ответы Re: B7 option  ("Inoue, Hiroshi" <inoue@tpf.co.jp>)
Список pgsql-odbc
Hi:
  I was using the last odbc driver (9.1.200) to get a character field with CR and LF.
With the following connection string, the last character was getting cut off (When a CR LF was in the fied).
Driver={PostgreSQL UNICODE};Server=
server.servicer.com;Port=5432;Database=dbname;Uid=user;Pwd=pwd;BI=2;TextAsLongVarchar=1;UnknownSizes=2;UseServerSidePrepare=1;
B0=254;B7=0;C5=1;

Changing the B7 to B7=0 corrects the issue (no cut off at the end)

Driver={PostgreSQL UNICODE};Server=
server.servicer.com;Port=5432;Database=dbname;Uid=user;Pwd=pwd;BI=2;TextAsLongVarchar=1;UnknownSizes=2;UseServerSidePrepare=1;
B0=254;B7=1;C5=1;

Documentation on the B7 is a little scarce but most say the B7 is the same as the TextasLongVarchar, but changing the
TextaslongVarcharhas no offection on this option.
 

What happens when the B7 is set 0?   (and textaslongvarhar=1)


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

Предыдущее
От: "Frank A. U."
Дата:
Сообщение: Re: UNICODE again
Следующее
От: "Jan-Peter Seifert"
Дата:
Сообщение: OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?