From: | Lachezar Dobrev <l(dot)dobrev(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Regression: Problems with Timestamp arguments |
Date: | 2013-09-10 11:56:00 |
Message-ID: | CA+xsaB0ObYETZMAqwvWhXpVEsn1EVQ0rWuFCYcU3dTog95wstw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
2013/9/10 Dave Cramer <pg(at)fastcrypt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2013-09-10 13:14:32 | Re: 9.3 driver |
Previous Message | Dave Cramer | 2013-09-10 11:23:38 | Re: Regression: Problems with Timestamp arguments |