| From: | "Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)de> |
|---|---|
| To: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Bug? Data Type Option 'Text as LongVarChar' not working anymore? |
| Date: | 2017-09-13 11:13:41 |
| Message-ID: | trinity-69a1b6c5-fa16-45c6-a4b7-57f51737b5df-1505301221305@3c-app-gmx-bs43 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hello,
> Gesendet: Mittwoch, 13. September 2017 um 02:05 Uhr
> Von: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)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)"
Newer psqlODBC versions (e.g. 09.06.04.00 / 09.06.04.10 / 09.06.05.00) always return data type "SQL_WVARCHAR (-9)" - irrespective of the 'Text As LongVarChar' setting.
I know that technically text is varchar without a length limit, but our software has to differentiate between these two data types.
Best regards,
Peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inoue, Hiroshi | 2017-09-13 11:49:19 | Re: Bug? Data Type Option 'Text as LongVarChar' not working anymore? |
| Previous Message | Georgy Pruss | 2017-09-13 09:23:02 | ODBC for Linux/RHEL - no 9.6.5 binary build yet? |