Re: BUG #17271: Updating enum columns type fails when constraints exist

Hi David,

Thanks for your quick response.
I believe it should fail.

However the error message should state that the constraint is blocking the
operation.
The current error message makes it hard to make a connection to the culprit.

The reason we did not go for ADD VALUE is that we use the same approach to
change all values at once by redefining the enum.
First ORM reasons which evolved to an internal standard (which we should
change based on your suggestion).

What do you think?

Le jeu. 4 nov. 2021 à 15:00, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
a écrit :

> On Thu, Nov 4, 2021 at 6:54 AM PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 17271
>> Logged by: Amaury Dumoulin
>> Email address: amaury(at)castordoc(dot)com
>> PostgreSQL version: 12.8
>> Operating system: alpine 3.14 on docker (host macOs 11.6)
>> Description:
>>
>>
> Any particular reason you didn't just use:
>
> ALTER TYPE name ADD VALUE [ IF NOT EXISTS ] new_enum_value [ { BEFORE |
> AFTER } neighbor_enum_value ]
>
> David J.
>