Re: "ERROR: operator is not unique" with Custom Data Type

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: "ERROR: operator is not unique" with Custom Data Type
Date: 2008-06-06 00:08:40
Message-ID: 42082FD0-30AC-4E26-BDA8-F0C464D9D99E@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 5, 2008, at 14:07, Martijn van Oosterhout wrote:

>> I'm sure I'm missing something simple here. How do I make it
>> assignment?
>
> # \h create cast
> Command: CREATE CAST
> Description: define a new cast
> Syntax:
> <snip>
> CREATE CAST (sourcetype AS targettype)
> WITHOUT FUNCTION
> [ AS ASSIGNMENT | AS IMPLICIT ]

I need to read up on the CAST documentation. Thanks.

>> Huh. That's what citext has, too:
>>
>> CREATE CAST (citext AS text) WITHOUT FUNCTION AS IMPLICIT;
>> CREATE CAST (text AS citext) WITHOUT FUNCTION AS IMPLICIT;
>
> And citext probably doesn't work with 8.3? The casting rules wrt text
> have changed...

Yes, that is correct. It builds, but the SQL doesn't all run properly.
I'll be wading through all those failures once I get the basics worked
out with v2.

Thanks,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-06-06 00:13:22 Re: Overhauling GUCS
Previous Message Tom Lane 2008-06-06 00:07:11 Re: About dependency reports in DROP RESTRICT