Re: Postgresql ODBC Truncates Timestamp second fractions
| От | Adrian Klaver |
|---|---|
| Тема | Re: Postgresql ODBC Truncates Timestamp second fractions |
| Дата | |
| Msg-id | 53416A78.4000006@aklaver.com обсуждение исходный текст |
| Ответ на | Re: Postgresql ODBC Truncates Timestamp second fractions (pg_gg@mailinator.com) |
| Список | pgsql-odbc |
On 04/05/2014 09:37 PM, pg_gg@mailinator.com wrote: > We have started with Oracle, but most probably they won't do much about > it as their ODBC driver handles timestamps properly, but not the Unicode > null character, which they have documented as a limitation, so it's hard > to press them on that. > > We were hoping to make it work by using the official PG ODBC driver, and > this driver although handles the problem of null character, has the > problem with timestamps. > > Unfortunately I don't think I'm getting relevant answer to my question > which is where we should look into the code to find out how the PG ODBC > driver handles paramter conversion and specifically SQLDescribeParam and > SQLBindParameter funnction calls. Well that is easy enough. Download the source and grep -E 'SQLDescribeParam|SQLBindParameter' * shows they are defined in odbcapi.c > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-odbc по дате отправления: