Perrin Harkins writes: > Actually, even this stuff could be put into a normalized "sessions" table > rather than serialized to a blob with Storable. It just means more work if > you ever change what's stored in the session.
This is a tough question. If you store it in a blob, you can't query it with an ad hoc SQL query. If you store it in a table, you have to deal with data evolution. On the whole, I vote for tables over blobs. My reasoning is that you have to deal with data evolution anyway. We have had about 200 schema changes in the last two years, and very few of them have had anything to do with user/visitor state. Rob
