Hi Jay, No, auto_vacuuming is off. And yes, the rows are gone, at least i couldn't find them anymore in those tables.
My database file is more than 50MB, and I only deleted records in 3 tables. And indeed, there are lots of indexes inside, so maybe you're right. On Sun, Dec 2, 2012 at 10:37 PM, Jay A. Kreibich <[email protected]> wrote: > On Sun, Dec 02, 2012 at 09:39:23PM +0100, Henry Huang scratched on the > wall: > > Good day everyone, > > > > I had a database file, and I deleted many records (tens of thousands) > from > > three tables, then, I did a VACUUM to that database. After I checked the > > size of the database file, I was a bit surprised that it's even (although > > slightly) bigger than before deletions. > > > > Is that possible? > > It is not all that unusual for a VACUUM to result in a slightly > larger database, especially with a DB that has a fair number of > indexes. This is usually not the case when rows have been deleted > from the database, however. > > Not to ask the obvious, but are you sure the rows were actually > deleted? Was auto-vacuuming on? > > -j > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Intelligence is like underwear: it is important that you have it, > but showing it to the wrong people has the tendency to make them > feel uncomfortable." -- Angela Johnson > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
