Closed dpage closed 2 years ago
dpage
commented
12 years ago Comment migrated from Redmine: https://redmine.postgresql.org/issues/574#note-1 Originally created by Guillaume Lelarge at 2012-01-07 18:57:33 UTC.
Redmine ticket header update:
| Name | Old Value | New Value |
|---|---|---|
| Status changed | New | In Progress |
dpage
commented
12 years ago Comment migrated from Redmine: https://redmine.postgresql.org/issues/574#note-2 Originally created by Guillaume Lelarge at 2012-01-07 19:03:55 UTC.
Fixed in http://git.postgresql.org/gitweb/?p=pgadmin3.git;a=commit;h=ac0dd7e5748860654136379f49b9962d0ec29dfb and http://git.postgresql.org/gitweb/?p=pgadmin3.git;a=commit;h=138e4503cc53cb029a81c46012b94c2a53070426
Redmine ticket header update:
| Name | Old Value | New Value |
|---|---|---|
| Status changed | In Progress | Resolved |
| Resolution changed | fixed |
dpage
commented
2 years ago Issue closed on Redmine.
Issue migrated from Redmine: https://redmine.postgresql.org/issues/574 Originally created by Thom Brown at 2011-07-22 15:23:22 UTC.
When going into a table's properties then editing an existing column, if any property is changed, after returning to the table properties dialogue, the SQL pane correctly shows the relevant changes. However, if you then go back to edit that same column, it will not reflect those new changes and be as if nothing had been touched. Therefore if, for example, you initially renamed the column, then went back into the column dialogue (without yet running the previous change) and added a comment, upon returning to the table properties dialogue for a second time, the SQL pane will only show the last change for that column and will have forgotten about the rename.