| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Rémi Aubel <remi(dot)aubel(at)gmail(dot)com>, 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 14:11:55 |
| Message-ID: | CADK3HH+z7hdV-85xwZTc=oKpB01fpdxVzD0XUV1B4KwLF=fVrA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토SQL : Postg토토SQL 메일 링리스트 : 2018-03-28 이후 PGSQL-BUGS 14:11 |
Remi,
See https://github.com/pgjdbc/pgjdbc/pull/1160
Dave Cramer
On 28 March 2018 at 09:59, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> 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.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Aubel | 2018-03-28 14:25:25 | Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement |
| Previous Message | David G. Johnston | 2018-03-28 13:59:26 | Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement |