Hello, Am I the only who get worry by this issue? Our database was full with 4 millions of sessions entries because of this !
I think the documentation should contains the SQL query to use for each sf versions. So upgrading from sf1.0.13 to sf1.0.1[4,5,6,7] is not safe for people using sfMySQLSessionStorage http://trac.symfony-project.org/ticket/3394 my 2c. Thomas On Fri, Aug 29, 2008 at 5:14 PM, Thomas Rabaix <[EMAIL PROTECTED]> wrote: > Hello, > > I just found out a bug in sfMySQLSessionStorage [1] , the session_time > use the mysql 'NOW()' function and before it was using php time(). > > Now the problem is most of snippets ( [2], [3]) found on the web to > used sfMySQLSessionStorage, use bigint to store the sess_time and not > a date field. > > So instead of saving '2008-05-06', it saved '2008'. and before the > revision it was '1206893684' (unix timestamp) > > So websites using bigint for sess_time fields will not have their > sessions deleted > > > [1] http://trac.symfony-project.org/changeset/8664 > [2] http://www.symfony-project.org/snippets/snippet/26 > [3] http://www.symfony-project.org/forum/index.php/m/20549/ > > -- > Thomas Rabaix > Internet Consultant > -- Thomas Rabaix Internet Consultant --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
