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 16:45:56
Message-ID: 45D33CC4.5040203@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> ANYENUM? What's the use-case for that?
>>>
>
>
>> Well ... *somebody* suggested it here ...
>> http://archives.postgresql.org/pgsql-hackers/2005-11/msg00457.php
>>
>
> Well, in that usage (ie, for enum I/O functions) it's not actually
> necessary that the type system as a whole understand ANYENUM as
> "something that any enum type can be cast to", because you're going to
> hot-wire the pg_type entries during CREATE ENUM anyway. What I'm
> wondering is if there's a use-case for it during ordinary user
> operations with enums.
>
>
>

If you look further down in the thread you'll see that I suggested
hiding it, because i didn't think there was much use case for it in user
code, but you didn't seem to think much of that idea.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2007-02-14 16:51:21 Re: NULL and plpgsql rows
Previous Message Neil Conway 2007-02-14 16:38:22 Re: Writing triggers in C++