| Lists: | pgsql-bugs |
|---|
| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | avkar(dot)moscow(at)gmail(dot)com |
| Subject: | BUG #17604: Constraints creation dialog column names do not refresh after changing names in the table |
| Date: | 2022-09-04 06:34:50 |
| Message-ID: | 17604-5cdfff30dff9a4cd@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17604
Logged by: Alexey Karaev
Email address: avkar(dot)moscow(at)gmail(dot)com
PostgreSQL version: 14.5
Operating system: Windows 10
Description:
I want to report an issue PostreSQL 14.5, pgAdmin 6.12. OS: Win 10.
1) Table created with 2 columns: column1 and column2
2) Opened dialog Constraints -> Create -> FOREIGN KEY...
3) Opened the list of the column names in the dialog Columns -> Local
Column.
4) Saw the correct names: column1 and column2.
5) Closed the dialog without saving
6) Renamed column names into: fk_column1, fk_column2
7) Repeated the steps 2 and 3
8) Saw the OLD names: column1 and column2 - they are not refreshed
The only way to refresh that column names inside constraints dialog is:
reopen the database (close and open pgAdmin).
Thank you for your support.
| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | avkar(dot)moscow(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17604: Constraints creation dialog column names do not refresh after changing names in the table |
| Date: | 2022-09-05 07:39:45 |
| Message-ID: | 84E8DEC5-0954-4286-93E1-486560748C05@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
> On 4 Sep 2022, at 08:34, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> The only way to refresh that column names inside constraints dialog is:
> reopen the database (close and open pgAdmin).
Bugs in pgAdmin should be reported to the pgAdmin team, see the below page for
more details:
https://www.pgadmin.org/support/
--
Daniel Gustafsson https://vmware.com/