Re: Regression: Problems with Timestamp arguments - Mailing list pgsql-jdbc

From Lachezar Dobrev
Subject Re: Regression: Problems with Timestamp arguments
Date
Msg-id CA+xsaB0ObYETZMAqwvWhXpVEsn1EVQ0rWuFCYcU3dTog95wstw@mail.gmail.com
Whole thread Raw
In response to Re: Regression: Problems with Timestamp arguments  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
2013/9/10 Dave Cramer <pg@fastcrypt.com>:
> Protocol 2 just does textual replacement of the parameters and does not use
> prepared statements on the server.

  I see…
  That would also answer another question about why null arguments
fail with the current protocol, but don't with protocol 2 (Hibernate
uses Serializable -> bytea which can not be used in any way).

> There is no way to degrade only certain parts. Why is it not possible to
> cast this to timestamp ?

  That works:
   SELECT CAST(? AS TIMESTAMP) IS NULL;

  However this is something that would mandate rewriting hundreds of
queries in a working (with protocol version 2) product.

> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca


pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Regression: Problems with Timestamp arguments
Next
From: Dave Cramer
Date:
Subject: Re: 9.3 driver