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

Bug #13127 The given dsn was not valid for MDB2
Submitted: 2008-02-15 16:23 UTC Modified: 2008-02-17 07:51 UTC
From: dustymugs Assigned: till
Status: Closed Package: HTTP_Session2 (version 0.7.0)
PHP Version: 5.2.4 OS: Linux 2.6.23.16
Roadmaps: 0.7.1    
Subscription  


 [2008-02-15 16:23 UTC] dustymugs (Bborie Park)
Description: ------------ MDB2 (v2.4.1) object passed to setContainer() not recognized as valid MDB2 object code is: HTTP_Session2::setContainer('MDB2', array('dsn' => &$dbo, 'table' => 'session_data')); Fixed by changing the "mdb2_common" string at line 108 of MDB2.php to "mdb2_driver_common" as that is the object type returned from MDB2. Actual result: -------------- Fatal error: Uncaught <table border="1" cellspacing="0"> <tr><td colspan="3" bgcolor="#ff9999"> <b>HTTP_Session2_Exception</b>: The given dsn was not valid in file /usr/local/lib/php/HTTP/Session2/Container/MDB2.php at line 115 in <b>/usr/local/lib/php/HTTP/Session2/Container/MDB2.php</b> on line <b>150</b></td></tr> <tr><td colspan="3" bgcolor="#aaaaaa" align="center"><b>Exception trace</b></td></tr> <tr><td align="center" bgcolor="#cccccc" width="20"><b>#</b></td><td align="center" bgcolor="#cccccc"><b>Function</b></td><td align="center" bgcolor="#cccccc"><b>Location</b></td></tr> <tr><td align="center">0</td><td>HTTP_Session2_Container_MDB2->connect(Object(MDB2_Driver_pgsql))</td><td>/usr/local/lib/php/HTTP/Session2/Container/MDB2.php:150</td></tr> <tr><td align="center">1</td><td>HTTP_Session2_Container_MDB2->open('', 'CSGSESSID')</td><td>unknown:unknown</td></tr> <tr><td align="center">2</td><td>session_start()</td><td>/usr/local/lib/php/HTTP/Session2.php:198</td></tr> <tr><td align="center">3</td><td>HTTP_Session2:: in /usr/local/lib/php/HTTP/Session2/Container/MDB2.php on line 116

Comments

 [2008-02-17 07:51 UTC] till (Till Klampaeckel)
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.