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

Поиск
Список
Период
Сортировка
От Amaury Dumoulin
Тема Re: BUG #17271: Updating enum columns type fails when constraints exist
Дата
Msg-id CAPqDOR9oskSayO-eiR1eyRpYXUqHbrA3rfBS7PSkc79WkS-HGA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17271: Updating enum columns type fails when constraints exist  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: BUG #17271: Updating enum columns type fails when constraints exist
Список pgsql-bugs
Дерево обсуждения
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.g.johnston@gmail.com> a écrit :
On Thu, Nov 4, 2021 at 6:54 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17271
Logged by:          Amaury Dumoulin
Email address:      amaury@castordoc.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.

В списке pgsql-bugs по дате отправления: