[eluser]arvid.janson[/eluser]
Currently I'm using DB-sessions, and it works OK. I do feel that adding flash_messages causes quite a bit overhead on my mysql-server, with a whole lot of unneccesary updates - for instance:
When a user tries to login, but fails, i use flash data to store the email, and a short message informing the user that something went wrong. The app uses one select and two updates to add the data (quite alright), and then one select and FOUR updates to retrieve it (I'm not writing anything new here, just getting the flash_data on a couple of places).
So ideally I would like to store some parts of the data (userinfo) using the database sessions, and some parts (flashdata messages) using "regular" session data. Is this possible? Or else, is there any way of dealing with this issue in a better way - a more effecient way of handling flash messages or better approach all together?
Regards,
Arvid
EDIT: Updated with a better title