Re: BUG #5490: INSERT doesn't force cast from text to timestamp - Mailing list pgsql-bugs

From Andy Balholm
Subject Re: BUG #5490: INSERT doesn't force cast from text to timestamp
Date
Msg-id B81304C8-D061-4A10-82C1-24257B3A79A6@balholm.com
Whole thread Raw
Responses Re: BUG #5490: INSERT doesn't force cast from text to timestamp  (Robert Haas <robertmhaas@gmail.com>)
Re: BUG #5490: INSERT doesn't force cast from text to timestamp  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Craig Ringer wrote:
> showing that your issue isn't actually with DISTINCT at all, but with Pg'=
s unwillingness to *implicitly* cast a value of explict text type to anothe=
r type.

Is there a way to make values of "undefined" type pass through the SELECT D=
ISTINCT filter (getting checked for uniqueness) but remain "undefined" if a=
ll the values supplied for the column are "undefined"? I don't know if the =
internal design of SELECT DISTINCT and the type system would allow for this=
, but if it would, it would take care of Farid's problem without introducin=
g implicit type casts.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Invalid YAML output from EXPLAIN
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Invalid YAML output from EXPLAIN