From 882b76bda8b701a8718960b8d639f060ae79e998 Mon Sep 17 00:00:00 2001
From: Greg Aker Which should provide for nominal performance gains if not autoloading packages. If you are using database sessions with the CI Session Library, please update your ci_sessions database table as follows:
-
+
Bug fixes for 2.0.3
@@ -86,6 +86,8 @@ Change Log
Version 2.0.2
diff --git a/user_guide/installation/upgrade_203.html b/user_guide/installation/upgrade_203.html
index 38cfb72c9..d7c0fae3a 100644
--- a/user_guide/installation/upgrade_203.html
+++ b/user_guide/installation/upgrade_203.html
@@ -94,6 +94,16 @@ Upgrading from 2.0.2 to 2.0.3
Update Sessions Database Tables
+
+
+ CREATE INDEX last_activity_idx ON ci_sessions(last_activity);
+
+
+
+
diff --git a/user_guide/libraries/sessions.html b/user_guide/libraries/sessions.html
index 8d9c14eb6..6048f4809 100644
--- a/user_guide/libraries/sessions.html
+++ b/user_guide/libraries/sessions.html
@@ -218,15 +218,17 @@ be updated, they can only be generated when a new session is created.
In order to store sessions, you must first create a database table for this purpose. Here is the basic prototype (for MySQL) required by the session class:
-Note: By default the table is called ci_sessions, but you can name it anything you want as long as you update the application/config/config.php file so that it contains the name you have chosen. -- cgit v1.2.3-24-g4f1b