Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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
