[Cgi-session-user] MySQL backend - multiple copies of session id's stored?

[Justin S. <ju...@sk...>]

Hey everyone,

before I delve any further into a problem I'm having,

Is it normal for the MySQL backend to store multiple copies of the  
session in a MySQL backend? The other backends I've tried - file, Db,  
Postgres, don't seem to have this behavior - I'm guessing this is  
because, the file backend has the name of the session_id as its  
filename, so any multiples get re-written - same goes for the  
Berkeley DB backend - keys (I think) in a tied hash have to be  
unique, or you'll overwrite your information already saved. No clue  
on Postgres ;)

I've had some bug reports:

	http://sourceforge.net/tracker/index.php? 
func=detail&aid=1525557&group_id=13002&atid=113002

that, for some reason, the more sessions that are saved, the more  
multiples of the next session created are made, perhaps in an almost  
Fibonacci growth :)

It gets to the point that many thousands of entries are made for the  
same session, slowing things right down. Before I blame CGI::Session,  
I was wondering if any specific behavior of my program may be at  
fault to create such a scenario.

Given the advice of the docs and this list, every change done to the  
sessions - adding/editing/removing is followed by a ->flush method  
call. I'm willing to make a test up that I'll try running, but first  
wanted to see if this is behavior is actually wrong. My program is of  
course, pretty meaty, so making a simplified version of what's going  
on, may be a little bit of a chore (that I am willing to do).

Justin Simoni
-- 
:: is an eccentric artist, living and working in Denver, Colorado
:: URL: http://justinsimoni.com
:: Mailing List - http://justinsimoni.com/mailing_list.html

ps: Sherzod - moved to the CGI::Session::ExpireSessions for my other  
problem - thanks!