ODBC Session store for Shibboleth SP, error with NameID insert
cantor.2 at osu.edu
Thu May 21 19:58:59 EDT 2015
On 5/21/15, 7:55 PM, "Michael A Grady" <mgrady at unicon.net> wrote:
>Will do. I figured it might be a condition that shouldn't arise if session management/cookies/everything else had worked as expected. Or that it could be a bug to do the search on a set of conditions that go beyond the key fields, and then assume one could insert a new record when that search doesn't return anything.
It can still arise because a lot of databases don't actually honor SERIALIZABLE transactions. If a select doesn't take a read lock over the table, then there's no way to prevent non-repeatable reads and the insert can still fail if another insert gets in between, which isn't allowed but happens anyway. But I don't know that that's what happened here, and if the only select is qualified by a where clause, that isn't sufficient to prevent a conflict even if there are no races.
More information about the users