Re: "anyelement2" pseudotype

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tom Dunstan <pgsql(at)tomd(dot)cc>, Matt Miller <pgsql(at)mattmillersf(dot)fastmail(dot)fm>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "anyelement2" pseudotype
Date: 2007-02-14 15:59:55
Message-ID: 45D331FB.5010703@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Tom Dunstan <pgsql(at)tomd(dot)cc> writes:
>
>> The enum patch [1] does exactly this with an ANYENUM pseudo-type. It
>> should provide a pretty good overview of what will be required.
>>
>
> ANYENUM? What's the use-case for that? These special cases in the
> type system are enough of a pain-in-the-neck for the code that I'm
> disinclined to add one without a very solid argument for it.
>

Well ... *somebody* suggested it here ...
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00457.php

;-)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian G. Pflug 2007-02-14 16:04:42 Re: Writing triggers in C++
Previous Message Tom Lane 2007-02-14 15:44:24 Re: "anyelement2" pseudotype