From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [pgAdmin III] #230: Combobox for FK column in the edit grid |
Date: | 2010-10-17 22:51:47 |
Message-ID: | 062.6908c7df6422cefa4d38b30facf1913a@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#230: Combobox for FK column in the edit grid
--------------------------+-------------------------------------------------
Reporter: Steffen Kuhn | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: editgrid | Platform: all
--------------------------+-------------------------------------------------
Comment(by brsa):
I agree with Steffen that this feature would be very useful in many cases.
If too many tuples in the lookup table or too many or exotic fields cause
trouble, its use could be restricted to simple cases.
Ideally, one could activate the lookup-feature for any field, defining
table & field to look up (fk constraint serving as default) and field(s)
to be displayed. But that raises the question where to save per-field-
settings ...
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/230#comment:2>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2010-10-18 18:50:32 | pgAdmin III commit: Use the AUI notebook on the query tool and debugger |
Previous Message | Dave Page | 2010-10-17 22:44:23 | pgAdmin III commit: Update the main form to use a wxAuiNotebook. This a |