Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.5.6
Bug #1358 Package doesn't overwrite expired sessions in DB
Submitted: 2004-05-07 05:09 UTC
From: denis at softservice dot org Assigned: troehr
Status: Closed Package: HTTP_Session
PHP Version: 4.3.6 OS: Linux
Roadmaps: (Not assigned)    
Subscription  
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:
MUST BE VALID
Solve the problem : 41 - 32 = ?

 
 [2004-05-07 05:09 UTC] denis at softservice dot org
Description: ------------ I'm using cookie enabled sessions. gc_probability is set to default (i.e. 1). After session expiration (cookie is still valid) and before gc run HTTP_Session_Container_DB class doesn't overwrite existing DB records with expired TS. Reason: SQL query in HTTP_Session_Container_DB::write compares record 'expiry' field with current TS, so it won't let write any information to it. It also won't create new record because SELECT query doesn't contain 'expiry' compare. Package v. - 0.4b.

Comments

 [2005-01-05 14:44 UTC] pear at netdevlabs dot com
This is the problem I also meat and have fixed. Today I have sent a mail to HTTP_Session developers with my fix (exactly like yours - remooving expiry from where clause in updating a session row) I hope they will fix it ASAP for all other users of this package.
 [2005-01-10 13:36 UTC] jason at greenhell dot com
Would it be possible to supply a patch for this fix? It could be helpful to others having this same problem - and possibly could be useful to the package maintainer.
 [2005-09-02 21:13 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 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.