[unixODBC-support] Was there a change in the time zone meaning of SQL_TIMESTAMP?

Nick Gorham nick at lurcher.org
Sat Nov 19 10:22:25 GMT 2016


On 18/11/16 20:21, Reza Taheri wrote:
>
> We have developed a performance benchmark (http://www.tpc.org/tpcx-v) 
> <http://www.tpc.org/tpcx-v%29> with PostgreSQL using ODBC in the 
> application. Everything was working fine up to
>
> ·postgresql93-9.3.5-2PGDG.rhel7
>
> ·postgresql93-odbc-09.03.0300-1PGDG.rhel7
>
> ·unixODBC-2.3.1-10.el7
>
> Then, someone took our kit, and installed it on a system with
>
> ·postgresql93-9.3.14-1PGDG.rhel7
>
> ·postgresql93-odbc-09.05.0200-1PGDG.rhel7
>
> ·unixODBC-2.3.1-11.el7
>
> ·A twist here may be that he may have loaded the database in one time 
> zone, later running the test from another time zone
>

I think this is likely to be a driver thing, the DM doesn't get involved 
with bound parameters by and large.

-- 
Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.unixodbc.org/pipermail/unixodbc-support/attachments/20161119/56f9c45e/attachment.html>


More information about the unixODBC-support mailing list