| 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-06 23:01:20 |
| Message-ID: | 054.e28f3d9705bf11b35265404f02c4b02f@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 thom):
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]
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/278#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2011-07-07 06:50:00 | Re: [pgAdmin III] #278: Support for updating enums |
| Previous Message | pgAdmin Trac | 2011-07-06 22:15:11 | Re: [pgAdmin III] #299: Crash on table refresh |