search

pgadmin-org / pgadmin3

Archive of the pgAdmin III project
https://www.pgadmin.org/
Other
178 stars 82 forks source link

Support for updating enums (RM #522) #292

Open dpage opened 14 years ago

dpage commented 14 years ago

Issue migrated from Redmine: https://redmine.postgresql.org/issues/522 Originally created by Guillaume Lelarge at 2010-11-13 22:44:49 UTC.

Seems it is as easy as doing an update on pg_enum. We should check that and, if it's true, make it work with pgAdmin.

dpage commented 13 years ago

Comment migrated from Redmine: https://redmine.postgresql.org/issues/522#note-1 Originally created by Thom Brown at 2011-07-06 23:01:20 UTC.

This is a bit vague, but I imagine it's referring to the fact that new values can be added to enums. If that's the case, this is already implemented: [http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=8dc53145d50ed2f65a112700c1390db79120f6d7]

dpage commented 13 years ago

Comment migrated from Redmine: https://redmine.postgresql.org/issues/522#note-2 Originally created by Guillaume Lelarge at 2011-07-07 06:50:00 UTC.

This is completely vague. The idea is that you don't need to be in 9.1 to update texts of an enum. The commit you're refering to is only for the support of the new syntax of ALTER TYPE targeting enum types. It's only available on 9.1. Moreover, it only allows one to add before or after an existing value. It doesn't allow someone to simply change a value of an enum.

I created this ticket to allow the update of a value in an enum. Which, if I'm not wrong, should be an UPDATE in pg_enum.