Elein Mustain
elein@xxxxxxxxxxx
510-637-9106
> On Mar 13, 2016, at 7:22 PM, Alvaro Herrera <alvherre@xxxxxxxxxxxxxxx> wrote:
>
> Elein wrote:
>
> Hi Elein,
>
>> * When an insert into an enum column fails give the person a hint as to valid values
>
>> -- Lousy message. Show enum list.
>> insert into badinfo values ('green');
>> ERROR: invalid input value for enum rainbow: "green"
>> LINE 1: insert into badinfo values ('green');
>
> True, we could improve that, though it could easily get messy with large
> enums.
>
>
>>> * Make enum_range to not be dependent on values in the target table.
>>> Remove/Obsolete enum_range( enum_column ) and replace with enum_range( typein regtype )
>>>
>>> Workaround: define the enum_range( typein regtyp ) yourself.
>
> Hmm, this is pretty clunky. I don't think passing the OID of the enum
> itself is a lot better, but if you use a regtype cast then perhaps it's
> not that bad. Perhaps we could have both functions.
I was thinking of this function in terms of the catalog functions like pg_get_functiondef which takes an oid. Obviosly all of those functions can take reg type with the actual name.
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
