Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Farid Zidan <farid(at)zidsoft(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail
Date: 2010-06-07 08:20:49
Message-ID: 87aar7b6e6.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
>> - other products are happy to solve the DISTINCT restriction without
>> any hint as far as what the datatype really is
>
> ... and so is Pg. That's not the problem; Pg complains after resolving the
> SELECT DISTINCT, when it finds that it's trying to insert values of type
> text' into a column with type 'timestamp'.

Ah yes. I've been paying more attention to the energy people have been
willing to put into helping the OP than into what the problem really
is. Thanks for clarifying.

--
dim

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Farid Zidan 2010-06-07 11:32:05 Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail
Previous Message Dean Rasheed 2010-06-07 08:14:43 Invalid YAML output from EXPLAIN