OK, now I am confused... On 4/18/07, Samuel R. Neff <[EMAIL PROTECTED]> wrote:
One thing to note is that the SQLite.NET wrapper by default issues all transactions as "BEGIN IMMEDIATE" so if you're running the SELECT within a transaction it will be within the context of an exclusive transaction (that's what BEGIN IMMEDIATE means, right?).
I plead ignorance: I don't actually know that much about Transactions. I had asked the list before, and it seems correct to ask again: should I be using Transactions for SELECT statements? They make sense for things that change the database, but what would be the reason when reading? I am currently NOT running the SELECTs inside Transactions. You can override this by using the wrapper-specific
BeginTransaction(deferred) override but it is not accessible if using the DbFactory standard interface. I completely agree with Dan that there is no way the wrapper is generating this error message, however behavior in the wrapper such as the above could be contributing to it.
By "Wrapper" are we talking about the same thing? DRH said that it IS the wrapper causing the problem, if by the wrapper we mean the .NET Managed Provider... if not, then I am just confused... HTH,
Sam
Thanks Sam, -- Joel Cochran
