Another option is to change the SQLite.NET wrapper to automatically retry on SQLITE_FULL error similar to the way it handles a schema error. Then it would be transparent to your app. It would have to close and reopen the connection of course, not just retry, but still the solution is manageable and can be encapsulated within the wrapper.
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 10:55 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Still getting "Insertion failed because database isfull." errors 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 ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
