Re: CAST Within EXCLUSION constraint - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: CAST Within EXCLUSION constraint
Date
Msg-id 2B33E1CB-26BA-4258-A9AC-9B5A137F02B0@justatheory.com
Whole thread Raw
In response to Re: CAST Within EXCLUSION constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Aug 21, 2013, at 4:13 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>> test=# create cast (source as oid) without function;
>> ERROR:  enum data types are not binary-compatible
>
> The reason for that is you'd get randomly different results on another
> installation.  In this particular application, I think David doesn't
> really care about what values he gets as long as they're distinct,
> so this might be an OK workaround for him.  But that's the reasoning
> for the general prohibition.

I’m okay with my function that casts to text, at least for now. An integer would be nicer, likely smaller for my index,
butnot a big deal. 

David




pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: PL/pgSQL, RAISE and error context
Next
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL, RAISE and error context