| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | amaury(at)castordoc(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17271: Updating enum columns type fails when constraints exist |
| Date: | 2021-11-04 13:58:04 |
| Message-ID: | CAKFQuwaY4CjKb=yHDMhSfER+y4P9p=vnC0PJ3Gdve5tewA15eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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:
>
> Error message upon failure
>
> With a sibyllin error message
> ERROR: operator does not exist: direction_state = direction_state_old
> HINT: No operator matches the given name and argument types. You might
> need
> to add explicit type casts.
>
> If we drop and recreate the constraint it works
>
>
This does not surprise me - why do you believe it is a bug? What should
happen?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-11-04 13:59:50 | Re: BUG #17271: Updating enum columns type fails when constraints exist |
| Previous Message | PG Bug reporting form | 2021-11-04 13:42:00 | BUG #17271: Updating enum columns type fails when constraints exist |