Re: Polymorphic types vs. domains

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Polymorphic types vs. domains
Date: 2009-02-04 19:29:29
Message-ID: 200902041929.n14JTTs07736@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> The proximate cause of this complaint:
> http://archives.postgresql.org/pgsql-general/2008-12/msg00283.php
> seems to be that the polymorphic-type code doesn't consider a domain
> over an enum type to match an ANYENUM function argument.
>
> ISTM this is probably wrong: we need such a domain to act like its base
> type for matching purposes. There is an analogous problem with a domain
> over an array type failing to match ANYARRAY; conversely, such a domain
> is considered to match ANYNONARRAY which it likely should not.
>
> Comments? If this is agreed to be a bug, should we consider
> back-patching it? (I'd vote not, I think, because the behavioral
> change could conceivably break some apps that work now.)

This has not been addressed yet.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2009-02-04 19:34:21 Re: patch to fix client only builds
Previous Message Jaime Casanova 2009-02-04 19:20:06 Re: LIMIT NULL