-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/10/11 14:03, PA Newsgroups wrote:
> Is there anything else that could cause this error? It's on a Windows
> computer if that makes any difference.
SQLite code has a tendency to report virtually any error involving write
calls as the disk
I have a customer with a database whose file size is about 39GB. He's
getting error 13 (database or disk is full) on an insert.
My app sets the page size to 4096, but even if it was the default, this
error shouldn't happen until it's around 4TB in size based on what I read
the default
what would cause this error?
I have a few users reporting it, all with different database file
sizes. is there a limit on row counts in 3.x ?
--
Cory Nelson
http://www.int64.org
e: [sqlite] Database Full!
"Greg Obleshchuk" <[EMAIL PROTECTED]> writes:
> Could you open a memory database and then attach the disk based database.
> Create the tables in the memory database and copy the rows from the disk
> based into memory. Once done detach
Hello,
it seems to me the solution would be: Create a special small file just
to protect some disc space. If you lack on disc space, delete the
protecting file (and hope nobody will steal the disc space inbetween)
and delete some records. Than again create the protecting file.
Obviously, in a
Benoit Gantaume wrote:
Hi,
I am trying to handle a problem that occurs when the disk is full:
when i try to insert, that return SQLITE_FULL.
Ok.
There is not problem to get some elements from the database.
Then I try to remove some elements...
But that returns SQLITE_BUSY!
I have tryed to
Hi,
I am trying to handle a problem that occurs when
the disk is full:
when i try to insert, that return
SQLITE_FULL.
Ok.
There is not problem to get some elements from the
database.
Then I try to remove some elements...
But that returns SQLITE_BUSY!
I have tryed to stop all
7 matches
Mail list logo
