DirectCheckAccess using its own connection

Jun 24, 2009 at 7:51 AM

Hi andrea,

in internalCheckAccess method, it creates its own connection instance and in this case transaction problems appear. Is this required for any reason ?



Jun 24, 2009 at 8:03 AM
internalCheckAccess method could be executed in async way ... so it need own connection.
Also CheckAccess just read ... so why you talk about transation problems ?

Andrea Ferendeles

Jun 24, 2009 at 8:32 AM

when unittesting, as I dont want to change db's current state, I beginTransaction, and rollback at the end of the test.  I think I just need to set isolation level of the transaction to allow read. Just wondered why it doesnt use storage's connection instance. Ok thanks.