Mikey C <[EMAIL PROTECTED]> wrote: > Not sure what you mean there DRH, but I set compression on one of my database > files on NTFS and file size shrunk from 1,289,216 bytes to 696,320 bytes. > > And of course the whole compression / decompression process is completely > transparent to SQLite and if you decide that compression is a bad thing, you > just uncheck the box on that file and you are back to where you started. >
After turning compression on, try making lots of updates to the database. Does the database stay the same size? Is there a significant I/O performance hit? I'm guessing that the answer in both cases will be "yes". Please let me know. -- D. Richard Hipp <[EMAIL PROTECTED]>
