| From: | Eduardo Pérez Ureta <edpeur(at)gmail(dot)com> |
|---|---|
| To: | "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 05:40:36 |
| Message-ID: | CAM7oS3H9gU0Gqvz9B9p6h22i8363z=Pv3bdDj74g7-9wmEw8tQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
On Oct 15, 2017 8:23 PM, "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sunday, October 15, 2017, Eduardo Pérez Ureta <edpeur(at)gmail(dot)com> wrote:
>
>> I understand that not sending the type for a parameter (when it is not
>> null) may not make much sense.
>> But, currently PostgreSQL accepts parameters with unknown types in
>> statements like:
>> INSERT INTO t1 (col1) VALUES (?)
>> SELECT * FROM t1 WHERE col1 = ?
>> where the column can be different types like VARCHAR or TIMESTAMP
>>
>
> col1 has a type and so the type of the unspecified variable can be
> inferred. Your is null example cannot have its typed inferred.
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2017-10-16 06:48:16 | Re: Improper const-evaluation of HAVING with grouping sets and subquery pullup |
| Previous Message | Andrew Gierth | 2017-10-16 03:50:15 | Re: Improper const-evaluation of HAVING with grouping sets and subquery pullup |