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

Bug #1016 Error on GC.
Submitted: 2004-03-15 10:01 UTC
From: fiw at mail dot ru Assigned: troehr
Status: Closed Package: HTTP_Session
PHP Version: 4.3.2 OS: WinXP
Roadmaps: (Not assigned)    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 38 - 36 = ?

 [2004-03-15 10:01 UTC] fiw at mail dot ru
Description: ------------ in HTTP\Session\Container\DB.php, 276 line - error. Reproduce code: --------------- if ($this->options['autooptimize']) { switch($this->db->type) { case 'mysql': ................... Expected result: ---------------- Notice: Undefined property: type in HTTP\Session\Container\DB.php on line 276 Actual result: -------------- if ($this->options['autooptimize']) { switch($this->db->phptype) { case 'mysql': ...................


 [2004-03-16 07:49 UTC] neufeind at php dot net
some more information from fiw: > fc DB-04-bug.php DB-04-wo-bug.php in function GC (in DB container) error. if set 'autooptimize' then check DB type ( switch($this->db->type) ), variable $type not defined in DB, so always autooptimise not run. you must use variable $phptype to detect type of database.
 [2004-07-11 22:16 UTC] gurugeek
Dear Maintainer, Your package http_session has currently 3 open bugs. We urge you to take the necessary steps to solve the reported issues at your soonest convenience. If the bug issue hasn’t been addressed yet you are kindly asked to take the necessary steps to ensure a prompt resolution of the problem. If you already addressed the reported problem feel free to change the bug status as soon as possible. Regards David Costa PEAR Quality Assurance
 [2005-09-02 21:12 UTC] torsten dot roehr at gmx dot de
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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.