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

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Farid Zidan <farid(at)zidsoft(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail
Date: 2010-06-07 03:17:07
Message-ID: 4C0C64B3.5080100@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I know it's not what you want (Pg behaving how you expect out of the
box) but creating implicit casts to the desired types will resolve your
immediate issue. You still have to run some Pg-specific code, but it can
be restricted to your DDL where there's (presumably) already plenty.

See:

http://www.depesz.com/index.php/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/

http://petereisentraut.blogspot.com/2008/03/readding-implicit-casts-in-postgresql.html

http://wiki.postgresql.org/images/d/d1/Pg83-implicit-casts.sql

--
Craig Ringer

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2010-06-07 08:14:43 Invalid YAML output from EXPLAIN
Previous Message Craig Ringer 2010-06-07 02:57:26 Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail