OK, I understand. This was my initial instinct, that it had to be coming from the Database, which was why I contacted DRH. His reponse was basically that my symptoms didn't match a problem in SQLite, given the other information at hand, and he is correct. So really, it isn't SQLite's problem OR the wrappers problem: it is the way the device handles its handles regarding the removable media.
I'm testing it now with moving the database to internal memory. Thanks, Joel On 4/18/07, Samuel R. Neff <[EMAIL PROTECTED]> wrote:
By wrapper I think we are all talking about the managed provider, SQLite.NET. This wrapper is not generating the error message--it is being reported to the wrapper by SQLite core. It is possible that the wrapper is contributing to the problem, but it is not generating the error. The SQLite3.Reset() method in the wrapper calls sqlite_reset(), handles the schema and locked errors, and then just passes along other errors. There's nothing in the code that can actually generate the error you reported. HTH, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: Joel Cochran [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:25 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Still getting "Insertion failed because database isfull." errors 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 ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
-- Joel Cochran
