From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [pgAdmin III] #278: Support for updating enums |
Date: | 2011-07-07 06:50:00 |
Message-ID: | 054.d56e46a7e564982ea795301b217ba5b0@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#278: Support for updating enums
---------------------+------------------------------------------------------
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: 1.12
Keywords: type | Platform: all
---------------------+------------------------------------------------------
Comment(by gleu):
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.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/278#comment:2>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-07-07 06:52:24 | Re: Wrong statistics for overloaded functions |
Previous Message | pgAdmin Trac | 2011-07-06 23:01:20 | Re: [pgAdmin III] #278: Support for updating enums |