Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type
От | Pavel Stehule |
---|---|
Тема | Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type |
Дата | |
Msg-id | CAFj8pRCzPgCQjiz1m2073_502jkOp-P4F6iG+cK8FVG_KhvGmg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type (Eduardo Pérez Ureta <edpeur@gmail.com>) |
Ответы |
Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type
|
Список | pgsql-bugs |
2017-10-16 17:24 GMT+02:00 Eduardo Pérez Ureta <edpeur@gmail.com>:
this case is one, where datatype cannot be detected from context, and Postgres requires it.
I have an application that I am trying to make it work in PostgreSQL and PostgreSQL seems to be the only database that does not support queries like:SELECT 1 WHERE ? IS NULLwith a Java setTimestamp parameter.You say PostgreSQL is strongly typed, but an unknown type is accepted in the cases I presented before. Do you mean that PostgreSQL is not following the SQL standard?
There is another question if there is not some issue on Java maybe JDBC side.
Regards
Pavel
On Oct 16, 2017 4:03 PM, "David G. Johnston" <david.g.johnston@gmail.com> wrote:My example is even better!There is no need to infer the type as it is not needed!PostgreSQL should be able to infer that no type is needed.It could - but since SQL is a strongly typed language it doesn't have that luxury.The original thread you pointed to complained about the regression from protocol v2 to protocol v3. Is that your complaint too or do you have some other use case?David J.
В списке pgsql-bugs по дате отправления: