shibboleth-dev - RE: ODBC store: transaction isolation levels
Subject: Shibboleth Developers
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: ODBC store: transaction isolation levels
- Date: Thu, 14 Feb 2008 18:28:07 -0500
- Organization: The Ohio State University
It looks to me like the initial focus should be on fixing the cause of the
errors you're getting here on just basic insert operations. That shouldn't
happen, and I think I know how to fix that without attacking the more
esoteric cases first.
I'm going to modify the code to use autocommit mode for all of the other SQL
operations except for the more obscure update case, which isn't used much.
That should prevent the race condition that Oracle is complaining about,
even on SERIALIZABLE. If you can test that for me on your install once I
check it in, we'll see how that works.
-- Scott
- ODBC store: transaction isolation levels, giacomo tenaglia, 02/14/2008
- RE: ODBC store: transaction isolation levels, Scott Cantor, 02/14/2008
- RE: ODBC store: transaction isolation levels, Scott Cantor, 02/14/2008
- RE: ODBC store: transaction isolation levels, Scott Cantor, 02/14/2008
- <Possible follow-up(s)>
- Re: ODBC store: transaction isolation levels, giacomo tenaglia, 02/14/2008
- RE: ODBC store: transaction isolation levels, Scott Cantor, 02/14/2008
- Re: ODBC store: transaction isolation levels, giacomo tenaglia, 02/14/2008
Archive powered by MHonArc 2.6.16.