Re: [ODBC] Bug? Data Type Option 'Text as LongVarChar' notworking anymore?
От | Inoue, Hiroshi |
---|---|
Тема | Re: [ODBC] Bug? Data Type Option 'Text as LongVarChar' notworking anymore? |
Дата | |
Msg-id | 4d336302-5fa2-3a28-04d6-152a453bfa42@dream.email.ne.jp обсуждение исходный текст |
Ответ на | Re: [ODBC] Bug? Data Type Option 'Text as LongVarChar' notworking anymore? ("Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de>) |
Ответы |
Re: [ODBC] Bug? Data Type Option 'Text as LongVarChar' notworking anymore?
|
Список | pgsql-odbc |
Hi, On 2017/09/13 20:13, Jan-Peter Seifert wrote: > Hello, > >> Gesendet: Mittwoch, 13. September 2017 um 02:05 Uhr >> Von: "Inoue, Hiroshi" <h-inoue@dream.email.ne.jp> > ... >> I can see the effect of 'Text As LongVarChar' here. >> Could you tell me unexpected behavior more concretely? > Test case: > 1. Create a DSN choosing 'PostgreSQL Unicode' > 2. Call ODBC-function SQLColumns(...) for a column of data type 'text'. > > Expected results as for e.g. version 09.03.04.00: > a) Option "Text As LongVarChar" NOT set => data type "SQL_WVARCHAR (-9)" > b) Option "Text As LongVarChar" set => data type "SQL_WLONGVARCHAR (-10)" How do you set *Unknown Sizes*, *Max Varchar* and *Max LongVarChar*? regards, Hiroshi Inoue > Newer psqlODBC versions (e.g. 09.06.04.00 / 09.06.04.10 / 09.06.05.00) always return data type "SQL_WVARCHAR (-9)" - irrespectiveof the 'Text As LongVarChar' setting. > > I know that technically text is varchar without a length limit, but our software has to differentiate between these twodata types. > > Best regards, > > Peter -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc
В списке pgsql-odbc по дате отправления: