Re: Postgresql ODBC Truncates Timestamp second fractions

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: pg_gg(at)mailinator(dot)com, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Postgresql ODBC Truncates Timestamp second fractions
Date: 2014-04-06 14:53:44
Message-ID: 53416A78.4000006@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 04/05/2014 09:37 PM, pg_gg(at)mailinator(dot)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(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Barry Bell 2014-04-07 12:28:19 Re: FW: ODBC 9.3.0210 not commiting, Discard ALL
Previous Message pg_gg 2014-04-06 04:37:55 Re: Postgresql ODBC Truncates Timestamp second fractions