[sqlite] Ann: SQLite Analyzer v 2.1.0 released

2004-02-17 Thread Sergey Startsev
Hello!

  SQLite Analyzer v 2.1.0 released.

  What's new in the version 2.1.0:
  
  - Table editing of the any size.
  - Fast scripts generation for commands INSERT, UPDATE, DELETE.

  Download url http://www.kraslabs.com/sqlite/files/sqlanlz.exe
  Screenshots http://www.kraslabs.com/sqlite/screen.html


-- 
Best regards

 Sergey Startsev
 SQLite Analyzer - GUI tool to manage SQLite databases.
 http://www.kraslabs.com/sqlite/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [sqlite] help! cant unsubscribe

2004-02-17 Thread Williams, Ken


> -Original Message-
> From: zeb warrior [mailto:[EMAIL PROTECTED]

> I've been unable to carrry out your request: The address
> 
>[EMAIL PROTECTED]
> 
> was already on the sqlite-users mailing list when I received
> your request, and remains a subscriber.



It looks like it's trying to subscribe you, not unsubscribe you.
Double-check that you're sending it the right instructions.

 -Ken

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [sqlite] Database Full!

2004-02-17 Thread Fred Williams
The only really safe way to compress the database would be to use an
incremental procedure similar to the familiar {to most :-) Windoze
"Defragment" disk utility.  The process needs to be reasonably fail safe and
disk miserly.  Until this feature is enhanced, one should remain vigilant as
to database size as one could quickly paint one's self into a corner in some
limited storage and embedded environments.

Fred

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 17, 2004 7:42 AM
To: Greg Obleshchuk
Cc: [EMAIL PROTECTED]
Subject: Re: [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 the database , delete it from disk .

If the machine crashes at this point, you're up that well known creek
without
a paddle...  I hope you have good backups. :-)

> Then create a disk based database , close it and attach it to the memory
> database and then do the reverse but only with the rows you want.

Derrell

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [sqlite] Database Full!

2004-02-17 Thread Jakub Adamek
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 live system this may fail ...

Jakub

D. Richard Hipp wrote:

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 stop all operation with: sqlite_interrupt(this->cdb);
But it seems to have no effect!
 
How can I free the database so that I can remove some elements from it?
 


DELETE requires some temporary disk space for the rollback journal.
So if your disk is full, you cannot delete.
Furthermore, just doing some DELETEs does not reduce the size of the
database file.  DELETE just adds some 1024-byte blocks of the file to
an internal freelist where they can be reused later for other purposes.
To actually reduce the size of the database file, you need to run
VACUUM after you DELETE.  VACUUM requires temporary disk space that
is a little over 2x larger than the size of the original database.
So (ironically) if you are low on disk space, VACUUM probably will
not run.
So, as you can see, it is difficult to get SQLite to run when you are
low on disk space.  Your best solution is to get a bigger disk.
A bigger disk drive is the right answer for your desktop, but for
an embedded solution (with perhaps a few MB of flash disk) that is
not practical.  That problem has been brought to my attention and
work is underway to make SQLite behave better in a low diskspace
environment.  Unfortunately, the changes to accomplish this will not
be available in the public version of SQLite for a least 3 more months
and probably longer than that.  Sorry.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]