[eluser]bretticus[/eluser]
Thanks @WanWizard. I had always assumed so because I never use cookie based sessions (even with encryption turned on.) Never took the time to find out (and wasn't going to poke around at the time of writing my reply.) Thanks.
I just want to reiterate. It's not a great idea to store
significant amounts of data in a database session either (I mean, you did say that you didn't want to make another trip to he database after all!) If you are storing queries, store them with op cache extensions (APC, memcache, etc.) If they are session specific, you could hash the username (or just use the session id) as keys for op cache. If you love the session idea, I'd recommend using PHP's session with memcached (this is only possible if your server is not shared. That is, you or someone in your company, has root access to do the set up.)
Of course, if the data isn't too large, even database enabled CI sessions are okay (because returning one column from one row with a primary key is always faster than performing a more complex query.)
