Re: BUG #14853: Parameter type is required even when the query does not need to know the type

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Eduardo Pérez Ureta <edpeur(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14853: Parameter type is required even when the query does not need to know the type
Date: 2017-10-16 16:32:57
Message-ID: a3bd5954-24d8-9f99-8cb6-fad9ddf02648@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 10/16/2017 05:24 PM, Eduardo Pérez Ureta wrote:
> 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 NULL
> with a Java setTimestamp parameter.
>

So you're passing a timestamp value to PostgreSQL only to find out if
it's NULL? I don't want to be rude, but that seems a bit ... strange.

>
> You say PostgreSQL is strongly typed, but an unknown type is accepted
> in the cases I presented before.
>

As David already pointed out before, these examples are not equal. In
the other cases PostgreSQL can easily infer the data type from other
parts of the query (e.g. target column in an INSERT). But that's not the
case here.

>
> Do you mean that PostgreSQL is not following the SQL standard?
>

Can you kindly point us to the part where SQL Standard requires the
behavior you're requesting?

thanks

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Eduardo Pérez Ureta 2017-10-16 17:39:31 Re: BUG #14853: Parameter type is required even when the query does not need to know the type
Previous Message Alvaro Herrera 2017-10-16 16:27:39 Re: BUG #14858: Inaccurate estimations after bulk delete and bulk insert