Probably you didn't realize that it is part of the SQL that SQLite understands: http://www.sqlite.org/lang_vacuum.html
Rani On Fri, 2005-02-11 at 15:28, [EMAIL PROTECTED] wrote: > > > My understanding is that a stupid question is the one not asked. > Excuse my ignorance, but what is VACUUM? > I've seen a couple of e-mails go back and forth and I feel silly not to > know what you guys are talking about. > Regards, > > Uriel_Carrasquilla > > > > > > "Cariotoglou > > Mike" To: > <sqlite-users@sqlite.org> > <[EMAIL PROTECTED] cc: > > ar.gr> Subject: RE: [sqlite] VACUUM > question > > > 02/11/2005 03:29 > > AM > > Please respond to > > sqlite-users > > > > > > > > > > It has been my experience that, when two processes have the same db > open, and one of them does a VACUUM, and the other tries to update, > The database gets corrupted. Not easy to simulate, but has happened at > least twice, in fact it has been the only way I managed to corrupt a > database. > Comments, DRH ? > > > -----Original Message----- > > From: D. Richard Hipp [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 10, 2005 12:14 AM > > To: sqlite-users@sqlite.org > > Subject: Re: [sqlite] VACUUM question > > > > On Wed, 2005-02-09 at 14:56 -0500, Luc Vandal wrote: > > > if my app has a sqlite3* pointer to the database and > > another app does > > > a VACUUM on the same database, will the pointer still be valid? > > > > Yes. > > > > > > > > > > Also, what if, while doing a VACUUM, a query executes on > > the database? > > > Will it just fail? > > > > You will get SQLITE_BUSY. > > -- > > D. Richard Hipp <[EMAIL PROTECTED]> > > > > > > > > > > > --
