[GitHub] tomcat issue #51: #41 Check and update session record if one already exists.

Github user alexisgayte commented on the issue: https://github.com/apache/tomcat/pull/51 I can see the point to lock the table in case of load balancing. But the previous version was deleting and inserting only. Will it not put down the perf as 90% are update? --- If your pro

[GitHub] tomcat issue #51: #41 Check and update session record if one already exists.

Github user ChristopherSchultz commented on the issue: https://github.com/apache/tomcat/pull/51 Might this be better written as `SELECT ... FOR UPDATE` with either `updateRow` or `ResultSet.insert` if there are no results from the `SELECT`? --- If your project is set up for it, you c

[GitHub] tomcat issue #51: #41 Check and update session record if one already exists.

Github user alexisgayte commented on the issue: https://github.com/apache/tomcat/pull/51 Hi Guys, I could not run the test but I use this code for my tomcat8. That will fix the issue #41. Also remove and create the session create some issue if you want to link the PK i