Re: [sqlite] SQL logic error when running vacuum;

This indeed is the problem! I just did a quick test and created a /var/tmp folder and now vacuum works fine. I can hoover databases to my hearts content Thanks again Dan, Scooby Hi Dan, I am running SQLite on an ARM9 target, cross compiled from windows using the OS_UNIX port out-of-the box

Re: [sqlite] SQL logic error when running vacuum;

Hi Dan, I am running SQLite on an ARM9 target, cross compiled from windows using the OS_UNIX port out-of-the box configuration save for defining SQLITE_OMIT_LOAD_EXTENSION. I am calling into SQLite from a test harness I implemented using the native API. I didn't realise that VACUUM generates a

Re: [sqlite] SQL logic error when running vacuum;

> database without error. > > > > --Preston > > - Original Message - > > From: "Preston Zaugg" <[EMAIL PROTECTED]> > > To: <sqlite-users@sqlite.org> > > Sent: Tuesday, October 04, 2005 10:58 AM > > Subject:

Re: [sqlite] SQL logic error when running vacuum;

e.org> > Sent: Tuesday, October 04, 2005 10:58 AM > Subject: RE: [sqlite] SQL logic error when running vacuum; > > >> Well, based on your comment i tried a vacuum from the API and i still get >> the error. >> >> Original Message Follows >> From: &q

Re: [sqlite] SQL logic error when running vacuum;

: "Preston Zaugg" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Tuesday, October 04, 2005 10:58 AM Subject: RE: [sqlite] SQL logic error when running vacuum; Well, based on your comment i tried a vacuum from the API and i still get the error. Original Me

RE: [sqlite] SQL logic error when running vacuum;

Well, based on your comment i tried a vacuum from the API and i still get the error. Original Message Follows From: "Cariotoglou Mike" <[EMAIL PROTECTED]> Reply-To: sqlite-users@sqlite.org To: <sqlite-users@sqlite.org> Subject: RE: [sqlite] SQL logic error when run

RE: [sqlite] SQL logic error when running vacuum;

as a matter of fact, I have also noticed that using the vaccum command from the command-line interface does bring this error up sometimes. however, since I use the graphical UI most of the time (being its author:) I don't use the command line interface that much. I suspect it has nothing to do