DB sessions, performances worries...

[eluser]alpar[/eluser]
Native sessions use the file system that is faster than the db, but less secure, especially on a shared host, the above solution might be good for you, but here are some alternatives:

You can use native sessions for non sensitive data (lie you mentioned) and keep db session for sensitive data (this will result in 2 session cookies, unless you set your own native session handlers, for php, but you loose some security, having 2 session cookies should be ok)

Also you can add a destructor to the session library if your run php5 to iterate with the database only at the beginning and the end of the lifetime. (if you don't set all session variables at once)