Re: Regression: Problems with Timestamp arguments

From: Thor Michael Støre <thormichael(at)gmail(dot)com>
To: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Cc: l(dot)dobrev(at)gmail(dot)com
Subject: Re: Regression: Problems with Timestamp arguments
Date: 2013-09-11 09:16:03
Message-ID: C69FA32A-4C33-4A90-BF5C-9FC42067F50B@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi,

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

Browse pgsql-jdbc by date

  From Date Subject
Next Message Jim Garrison 2013-09-11 15:59:35 Re: CopyManager API?
Previous Message Lachezar Dobrev 2013-09-11 07:12:39 Re: Regression: Problems with Timestamp arguments