I don't understand what you mean by fine-grained, please elaborate.
I basically mean, "don't use the session as your cache."
Aparts from that, I think to use a session to store authentication, login state
and user association is about the best usage one can make of a session. There's
little else that occurs to me requiring a session at all.
Okay. And there's nothing there that requires "for update."
Really, if a user logs in twice concurrently, just let the one of the updates overwrite the first. That happens anyway if you use "for update;" it just happens a little slower. :)
Quoting Michael Bayer <[EMAIL PROTECTED] >:
> if you have a big application with multiple servers and
> all, its often better to represent user-oriented concepts in a more
> explicit and fine-grained way rather than a serialized (the other
> kind of serialized) BLOB.
--
Jonathan Ellis
http://spyced.blogspot.com
