Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.3.7

Bug #13081 Reopen #11504: MDB2+Tree problem. MDB2 doesn't contains getTextValue method
Submitted: 2008-02-06 23:48 UTC
From: redmoskito Assigned: dufuz
Status: Closed Package: Tree (version 0.3.2)
PHP Version: 5.2.4 OS: Linux, Ubuntu 7.04
Roadmaps: (Not assigned)    
Subscription  


 [2008-02-06 23:48 UTC] redmoskito (Kyle Simek)
Description: ------------ Still getting this error while calling $tree->move(). Using Memory_MBD2simple. A quick text search in Dynamic/MDB2nested.php shows the calls to getTextValue() on lines 192 and 593. Fixed by changing these to quote(). Test script: --------------- $nested_tree = TREE::setup('Memory_MDB2nested', 'mysqli://username@localhost/table', array('table' => 'app_paths', 'order' => 'name', 'columnNameMaps' => array( 'id' => 'table_id', 'asdf' => 'parentid' ))); $nested_tree->setup(); $tree->move(2,1); Expected result: ---------------- Tree node 2 gets moved to be under parent node 1. Actual result: -------------- Error message: Fatal error: Call to undefined function: MDB2_Driver_mysqli::getTextValue(). in /home/ksimek/scholarship_portal/src/includes/library/Pear/MDB2.php on line 1936

Comments

 [2008-03-23 07:38 UTC] doconnor (Daniel O'Connor)
Just a footnote; getTextValue() is for MDB, not MDB2
 [2008-03-23 07:45 UTC] doconnor (Daniel O'Connor)
Helgi, http://cvs.php.net/viewvc.cgi/pear/Tree/Dynamic/?hideattic=0 Is that a merge error, or is that intentional?
 [2008-03-23 15:50 UTC] dufuz (Helgi Þormar Þorbjörnsson)
No merge errors, just a new feature release that I never found time to throw out the door, keep conversations like this in emails not bug report comments.
 [2008-03-23 16:02 UTC] dufuz (Helgi Þormar Þorbjörnsson)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.