On Mon, Jun 7, 2010 at 3:52 PM, Robert Haas wrote:
>> Is there a way to make values of "undefined" type pass through the SELECT
>> DISTINCT filter (getting checked for uniqueness) but remain "undefined" if
>> all the values supplied for the column are "undefined"?
The concept of "uniqueness" de
On Jun 7, 2010, at 7:53 AM, Tom Lane wrote:
> Andy Balholm writes:
>> Is there a way to make values of "undefined" type pass through the
>> SELECT DISTINCT filter (getting checked for uniqueness) but remain
>> "undefined"
>
> No. What is your criterion for deciding that two values are distinct?
Andy Balholm writes:
> Is there a way to make values of "undefined" type pass through the
> SELECT DISTINCT filter (getting checked for uniqueness) but remain
> "undefined"
No. What is your criterion for deciding that two values are distinct?
It's not possible to do that without imputing a data
On Mon, Jun 7, 2010 at 10:30 AM, Andy Balholm wrote:
> 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 another
>> type.
>
> Is there a way to make values of "undefined" type pa
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 another
> type.
Is there a way to make values of "undefined" type pass through the SELECT
DISTINCT filter (getting checked for un
