Hi All, I am using sqlite-amalgamation-3_7_3.zip source in my project. I tested VACUUM command on a DB file which has lot of holes(fragmentation caused by deletion of random records ) but the source file size does not change. Instead sqlite applies the vaccum command and writes data into new temporary file prefixed by "etilqs_".
Input:MyDb.db with size 23KB (has lot of empty pages caused due to delete operation) *Expected OutPut: after applying Vacuum command, should be MyDb.db with reduced file size of 13KB.* *Actual output: MyDb.db remains size 23KB(size not changes from original) and creates temporary file etilqs_Hm4RUi6JPXcMZ17 whose data is same as MyDb.db but the size is reduced to 13KB* I applied the VACUUM command on MyDb.db using sqlite3.exe(shell based commands interpreter) and it applies to the MyDb.db whose size beccomes 13KB after the command completion. ? I have ported sqlite-amalgamation-3_7_3.zip on some X platform using WINCE configuration. Everything else seem to work fine except this strange behaviour of VACUUM feature. Is this a bug or i am doing something wrong? Why sqlite writing data of MyDb.db in to temporary file and applying VACUUM on temporary file instead of original file? Please let me know if any of you come across such scenario and have solution for this issue. Thanks a lot. ~Sudha _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users