On 4/18/07, Dan Kennedy <[EMAIL PROTECTED]> wrote:If the win32
SetFilePointer() function fails (used to position the
"pointer" at a given file offset, which SQLite does as part of a
SELECT) SQLite assumes the reason is that the disk is full and
returns SQLITE_FULL. This is probably what's
: 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, whi
> -Original Message-
> From: Christian Schwarz [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 18, 2007 7:25 AM
> To: sqlite-users@sqlite.org
> Subject: AW: [sqlite] Still getting "Insertion failed because database
> isfull." errors
>
> > the database residing on removable media. When
I was able to recreate this problem on the testing device (but NOT in DEBUG,
of course). I pulled up the application, did some operations, and then let
the device go to sleep. I then powered back up, and the first operation I
tried to do threw the error.
Joel
On 4/18/07, Christian Schwarz
sition 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.&
Or you can close the database connection if it's idle for a little bit (less
than it takes for it to sleep)?
On 4/18/07, Joel Cochran <[EMAIL PROTECTED]> wrote:
OK, then I won't be worrying about Transactions for SELECT statements, it
doesn't really apply to our application.
And some
OK, then I won't be worrying about Transactions for SELECT statements, it
doesn't really apply to our application.
And some additionaly confirmation that Christian seems to have been right on
key: according to the problems reported at the System.Data.SQLite forums,
the problem is most likely due
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
"Joel Cochran" <[EMAIL PROTECTED]> wrote:
> should I be using
> Transactions for SELECT statements?
The only reason to use a transaction around SELECT statements
is if you want to make sure that the database is not changed
by another process in between consecutive SELECTs.
It used to be the
PROTECTED]
Sent: Wednesday, April 18, 2007 1:25 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Still getting "Insertion failed because database
isfull." errors
> At first I thought this had solved the problem, because all in house
testing
> runs beautifully. However, as
10 matches
Mail list logo
