databases. It seems that the logout error was cured, in that if you reload the
database while logged in, you shouldn't get an error when returning to the
site. I don't know how the session plugin we're using will be working with the
new storage method.
<div id="voters" class="main-section">
<div id="voters-content">
<h2>Voters</h2>
<div id="voters" class="main-section">
<div id="voters-content">
<h2>Voters</h2>
# Use the database for sessions instead of the file system
# (create the session table with 'rake db:sessions:create')
# Use the database for sessions instead of the file system
# (create the session table with 'rake db:sessions:create')
- # config.action_controller.session_store = :active_record_store
+ config.action_controller.session_store = :active_record_store
# Use SQL instead of Active Record's schema dumper when creating the test database.
# This is necessary if your schema can't be completely dumped by the schema dumper,
# Use SQL instead of Active Record's schema dumper when creating the test database.
# This is necessary if your schema can't be completely dumped by the schema dumper,
+# CREATE sessions TABLE
+######################################
+
+drop table if exists sessions;
+create table sessions (
+ id int(11) NOT NULL auto_increment,
+ sessid varchar(255),
+ data text,
+ updated_at datetime DEFAULT NULL,
+ primary key (id),
+ index session_index (sessid)
+);
+
# CREATE users TABLE
#####################################
#DROP TABLE IF EXISTS `users`;
# CREATE users TABLE
#####################################
#DROP TABLE IF EXISTS `users`;