Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement
От | Dave Cramer |
---|---|
Тема | Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement |
Дата | |
Msg-id | CADK3HHL04oRUsW1phsqef4LsKnHv7nnR6_UU-FXkF=srwnKnjA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement (Rémi Aubel <remi.aubel@gmail.com>) |
Список | pgsql-bugs |
@Remi,
You are welcome. It would be wonderful it you could test the fix ?
Dave Cramer
On 28 March 2018 at 10:25, Rémi Aubel <remi.aubel@gmail.com> wrote:
Oh Thanks, Dave!I had created the issue on GitHub (https://github.com/pgjdbc/pgjdbc/issues/1161) and saw you marked it as duplicate. --Le mer. 28 mars 2018 à 16:12, Dave Cramer <davecramer@gmail.com> a écrit :Dave CramerOn 28 March 2018 at 09:59, David G. Johnston <david.g.johnston@gmail.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.
В списке pgsql-bugs по дате отправления: