From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
---|---|
To: | Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Bug? Data Type Option 'Text as LongVarChar' not working anymore? |
Date: | 2017-09-13 23:05:01 |
Message-ID: | 6d56a09b-a42f-1d8e-8e88-28c57376db44@dream.email.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi,
On 2017/09/13 23:34, Jan-Peter Seifert wrote:
> Hello,
>
>> Gesendet: Mittwoch, 13. September 2017 um 15:47 Uhr
>> Von: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>
>
>> Could you set *Max LongVarChar* to 65535?
> Thank you very much! This workaround does work. We decreased Max Varchar to 65533 instead though.
> It still seems like a bug to me though.
Hmm, I want to eliminate *Text as LongVarChar*, *Unknowns as
LongVarChar* or *Unknown Sizes* option if possible.
BTW *UNKNOWNS as LongVarChar* option(default off) would be INVALID for
PG10 servers.
Are there any problems?
Because 'unknown' type would be 'text' type in PG10, 'unknown' items
before would be controlled
by *Text as LongVarChar* option(default on).
regards,
Hiroshi Inoue
>
> Best regards,
>
> Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Sufiyan, Moz | 2017-09-15 17:39:55 | Error Notification |
Previous Message | Jan-Peter Seifert | 2017-09-13 14:34:37 | Re: Bug? Data Type Option 'Text as LongVarChar' not working anymore? |