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 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 temp file. I don't have a /var/tmp
folder on my file system. I will check where by default SQLite creates it's
temp file and either create the folder it needs or change where it creates
it's temporary file.

That might just be the problem.

Thanks and regards,

Scooby


Dan Kennedy-4 wrote:
> 
> On Tue, 2007-07-24 at 04:22 -0700, scoobyjh wrote:
>> With OS_UNIX version 3.4.0 (AMALGAMATION), I do the following:
>> 
>> a) open a database file, it contains one table with 3 records in it.
>> b) insert 9997 records in side a begin/end transaction
>> c) delete 9997 records
>> d) vacuum the database
>> e) close the database file
>> 
>> Whether I use VACUUM on it's own or VACUUM table-name, I get this error:
>> 
>> SQL error: SQL logic error or missing database
>> 
>> I have no views and I havn't changed the schema.
>> Any ideas?
> 
> What are you doing this with? An application, or via the sqlite
> shell?
> 
> Vacuum creates a temporary database file, usually in /var/tmp/.
> Is there sufficient free space there (and are the permissions
> sane)? In this case "sufficient free space" means enough space 
> to make a copy of the original db file.
> 
> Dan.
>  
> 
> 
> 
:-):-):-)
-- 
View this message in context: 
http://www.nabble.com/SQL-logic-error-when-running-vacuum--tf373521.html#a11766336
Sent from the SQLite mailing list archive at Nabble.com.


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to