Обсуждение: [pgAdmin III] #230: Combobox for FK column in the edit grid

#230: Combobox for FK column in the edit grid
--------------------------+-------------------------------------------------
 Reporter:  Steffen Kuhn  |       Owner:  dpage
     Type:  bug           |      Status:  new  
 Priority:  minor         |   Milestone:       
Component:  pgadmin       |     Version:  trunk
 Keywords:  editgrid      |    Platform:  all  
--------------------------+-------------------------------------------------
 If a column has a forgein key the "editor" should be a combobox filled
 with the entries of the lookup table.

 Sure there may be a pitfall if the lookup table has many entries. In this
 the feature may probably disabled by the
 application options. But in most cases there will be additional benefit.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/230>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

#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  
--------------------------+-------------------------------------------------
Changes (by gleu):

  * type:  bug => feature


--
Ticket URL: <http://code.pgadmin.org/trac/ticket/230#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

#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