Community Page
- blog.kovyrin.net Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- nice article! nice site. you're in my rss feed now ;-) keep it up
- nice article! nice site. you're in my rss feed now ;-) keep it up
- nice article! nice site. you're in my rss feed now ;-) keep it up
- Top post. Thank you very much. :-)
- Thanks for the info. May God have mercy on us all.
Jump to original thread »
How often do we think about our http sessions implementation? I mean, do you know, how your currently used sessions-related code will behave when sessions number in your database will grow up to millions (or, even, hundreds of millions) of records? This is one of the things we do not
... Continue reading »
1 year ago
Thanks.
1 year ago
1 year ago
1 year ago
1 year ago
@@connection.execute "DELETE FROM #{table_name} WHERE UNIX_TIMESTAMP(updated_at)
1 year ago
Note the UNIX_TIMESTAMP around (updated_at) in first part of the comment
1 year ago
[application.rb]
# turn off sessions if this is a request from a robot
session :off, :if => proc { |request| request.user_agentuser_agent =~ /\b(Baidu|Gigabot|Googlebot|libwww-perl|lwp-trivial|msnbot|SiteUptime|Slurp|WordPress|ZIBB|ZyBorg)\b/i }
1 year ago
After that application don't get back alive, until I delete session record.
1 year ago
Unfortunately, my MySQL database was not compiled with InnoDB.
1 year ago
1 year ago
12 months ago