From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CAST Within EXCLUSION constraint |
Date: | 2013-08-21 15:30:09 |
Message-ID: | 2B33E1CB-26BA-4258-A9AC-9B5A137F02B0@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Aug 21, 2013, at 4:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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, but not a big deal.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-08-21 15:34:59 | Re: PL/pgSQL, RAISE and error context |
Previous Message | Merlin Moncure | 2013-08-21 15:18:24 | Re: PL/pgSQL, RAISE and error context |