Tickets :: [#5317] dblookup field extension

6.0.0-alpha10

5/14/25

Search Results: 2 of 9 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

Summary	dblookup field extension
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Enhancement
State	Accepted
Priority	1. Low
Owners
Requester	duck (at) obala (dot) net
Created	04/30/2007 (6589 days ago)
Due
Updated	04/01/2008 (6252 days ago)
Assigned
Resolved
Milestone
Patch	Yes

04/01/2008 03:17:11 AM	Chuck Hagenbuch	Patch ⇒ Yes

03/31/2008 10:23:46 PM	Jan Schneider	State ⇒ Accepted

03/31/2008 07:58:36 PM	pp (at) dia (dot) uva (dot) nl	Comment #4 New Attachment: Form.php.diff	Reply to this comment
Hey, here's another implementation of the suggested improvement of the dblookup form type so it can properly handle foreign keys (not just in cases where the key equals the value).

05/12/2007 08:50:30 PM	Chuck Hagenbuch	Comment #3 State ⇒ Rejected	Reply to this comment
Marking as rejected for now. Might be superceded by new Horde_Form with helpers, might not be.

05/02/2007 12:06:23 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
This breaks the old behavior. getAll() returns a two dimensional array, even if you query only a single column. getCol() returns a simple array. Beside that, the error check is wrong because it evaluates to true if $results is a PEAR_Error.

04/30/2007 02:20:20 PM	Duck	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ dblookup field extension Queue ⇒ Horde Framework Packages New Attachment: dblookup.diff State ⇒ New	Reply to this comment
Be more flexible in the dblookup field. Now we retrieve only the first column, with this patch if the second column is returned by the query, it would be used as option name.