Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Rémi Aubel <remi(dot)aubel(at)gmail(dot)com>
Cc: Postgres Bug <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement
Date: 2018-03-28 13:59:26
Message-ID: CAKFQuwYExm4G2Ejn6GDPjKuG-1Ayk8gvBiutrUpKn+QU76oX+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 28, 2018 at 6:26 AM, Rémi Aubel <remi(dot)aubel(at)gmail(dot)com> wrote:

> I need to bind a UUID parameter which may be null in a statement like
> "select * from test table where ? is null or ? = c_uuid".
> Whatever approach I use, the driver rejects my request with "ERROR: could
> not determine data type of parameter $1".
> ​[...]​
> But in the current implementation of the driver, the
> PreparedStatement.setNull(int, int, String) delegates to setNull(int, int)
> so that specifying the type name has no effect.
>

​JDBC Driver bugs are off-topic for this list. They should be reported on
the project's GitHub site's Issues List.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2018-03-28 14:11:55 Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement
Previous Message Rémi Aubel 2018-03-28 13:26:48 BUG: Unable to bind a null value typed as a UUID in a PreparedStatement