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

From Thor Michael Støre
Subject Re: Regression: Problems with Timestamp arguments
Date
Msg-id C69FA32A-4C33-4A90-BF5C-9FC42067F50B@gmail.com
Whole thread Raw
In response to Regression: Problems with Timestamp arguments  (Lachezar Dobrev <l.dobrev@gmail.com>)
List pgsql-jdbc
Hi,

On 11. sep. 2013, at 08:37, pgsql-jdbc-owner@postgresql.org wrote:
From: Lachezar Dobrev <l.dobrev@gmail.com>
Subject: Re: Regression: Problems with Timestamp arguments
Date: 10. september 2013 13:07:28 CEST
To: Dave Cramer <pg@fastcrypt.com>


 This works:
  PREPARE is_date_reached AS SELECT NOW() < $1 OR $1 IS NULL;

 However JDBC can not use the same parameter more than once…
  SELECT NOW() < ? OR ? IS NULL;

 Hmm. That's not good.

How about:
SELECT NOW() < ? OR $1 IS NULL;

I've at least always managed to use the same parameters over again like that in JDBC under normal circumstances, thought that's been with types the driver knew about.

Thanks, Thor Michael

pgsql-jdbc by date:

Previous
From: Lachezar Dobrev
Date:
Subject: Re: Regression: Problems with Timestamp arguments
Next
From: Jim Garrison
Date:
Subject: Re: CopyManager API?