Shibboleth Developers

["Scott Cantor" <>]

After a bit of research, it turns out Oracle in their infinite wisdom thinks
that "serializable" is just kind of a nice theory but doesn't actually
implement it anyway. They won't give you a read lock unless you add "for
update" to your select. (I'm sure locking you into Oracle has nothing to do
with that, it's all for your benefit. Sigh.)

In a nutshell, I need to review the various operations and see exactly what
the issues will be. Since I have versioning built into the storage model, I
may be able to prevent non-repeatable reads anyway, and just shift the more
common errors your seeing to that rarer case.

I didn't spend the time because I thought serializable meant, well,
serializable. Which it does in most databases.

-- Scott