Re: B7 option

From: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>
To: Barry Bell <Barry_Bell(at)harte-hanks(dot)com>
Cc: "Frank A(dot) U(dot)" <fau(at)email(dot)com>, psql-odbc <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: B7 option
Date: 2013-08-01 03:20:19
Message-ID: 51F9D3F3.60807@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Barry,

(2013/07/31 23:29), Barry Bell wrote:
> 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;

Contradictory options TextAsLongVarchar=1 and B7=0 are specified.
Psqlodbc drivers eat the tokens one by one and overwrite the former
option by the latter one after all.

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

Changing to B7=1?

> 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 TextaslongVarchar has no offection on this option.
>
> What happens when the B7 is set 0? (and textaslongvarhar=1)

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2013-08-01 10:55:27 Re: OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?
Previous Message Jan-Peter Seifert 2013-07-31 15:32:53 OIDs > 2147483647 still a problem for the Unicode version ( 32 bit ) ?