Github user JohnKiel commented on the issue:
https://github.com/apache/tomcat/pull/41
If you use SELECT FOR UPDATE, then you'll also need to start and commit a
transaction, with the overhead that entails. If the record is modified or even
deleted between the time the SELECT query and UPDATE, it's of little to no
consequence, and no worse than the current delete/insert method. The worst
result would be slightly stale session data being written, which is kind of an
issue anyway if you have an application with that many threads all trying to
save data for the same session at basically the same time.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
