From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #369: Edit data and tables with a unique key |
Date: | 2012-07-14 12:57:35 |
Message-ID: | 045.dd5bcd46d527dc0336350de58f4f9241@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#369: Edit data and tables with a unique key
----------------------+-----------------------------------------------------
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: editgrid | Platform: all
----------------------+-----------------------------------------------------
I have a feature request for the 'Edit data' window that is available for
each table in pgAdmin.
As the OID column is not guaranteed to contain unique OIDs it would be
nice to have additional/other fallback options ( via check box in
pgAdmin's general options? ) to identify rows for editing in tables
without primary keys.
I'd suggest serials ( serial/serial4 and bigserial/serial8 ) or unique
columns/constraints.
Another drawback of OID columns is that you can't add them afterwards.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/369>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2012-07-14 13:01:56 | [pgAdmin III] #370: pgScript error when relation name contains ")" symbol |
Previous Message | Guillaume Lelarge | 2012-07-14 12:46:10 | pgAdmin III commit: Fix freeze of UI when querytool has an error on a q |