El Forum
04-29-2011, 01:05 PM
[eluser]SneakyDave[/eluser]
Regarding this old thread: http://ellislab.com/forums/viewthread/87567/
I found out that my installation of CI 1.7.2 and 1.7.3 was caching queries to the session table if DB caching was turned on.
Naturally, this caused a lot of problems because there wasn't any code in the sessions class to turn caching off when selecting from the session table. I can turn off caching in the controller, but it doesn't solve the problem because the session class has already done it's work in bringing the session into the controller.
Does this still exist in CI 2.0x? Or is there a reason it hasn't been fixed, or is there some other problem?
I can verify that the problem is with the db caching because on page refreshes, the session class is loaded, but there aren't any queries done to the database, so it must be picking up the cached session, which may or may not look anything like the session stored on the table.
Just confused. Thanks for any help.
Regarding this old thread: http://ellislab.com/forums/viewthread/87567/
I found out that my installation of CI 1.7.2 and 1.7.3 was caching queries to the session table if DB caching was turned on.
Naturally, this caused a lot of problems because there wasn't any code in the sessions class to turn caching off when selecting from the session table. I can turn off caching in the controller, but it doesn't solve the problem because the session class has already done it's work in bringing the session into the controller.
Does this still exist in CI 2.0x? Or is there a reason it hasn't been fixed, or is there some other problem?
I can verify that the problem is with the db caching because on page refreshes, the session class is loaded, but there aren't any queries done to the database, so it must be picking up the cached session, which may or may not look anything like the session stored on the table.
Just confused. Thanks for any help.