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]
