Stickman Posted November 16, 2006 Posted November 16, 2006 (edited) I'm using the SQLite UDF in a small app I'm writing. It's all gone very well so far, but I've stumbled across a problem and nothing I do seems to help.Here's a simplified summary of what I'm doing:1) First, I'm reading a sequence of rows from a table2) Then, I'm writing a new row to the table3) Finally I'm running the same read query as in 1)...and it appears to have worked -- the new row is there. However if I quit the app and restart, the row is gone.And...if I just quit the app and look in the folder where the db file is stored, I have a new file called my_db_file.db3-journal. From what little I know of SQLite I'm guessing there's some locking problem but I can't seem to find any way to fix it (if this indeed even the case).Can anyone tell me what's going on? I'm banging my head on the desk here. Edited November 16, 2006 by Stickman
piccaso Posted November 16, 2006 Posted November 16, 2006 maybe you use temp tables or the transction isnt finished... if you post your code i may be able to find out CoProc Multi Process Helper libraryTrashBin.nfshost.com store your AutoIt related files here!AutoIt User Map
Stickman Posted November 17, 2006 Author Posted November 17, 2006 (edited) I just tried adding a call to SQLite_Close() just before the insert and it returned 5 ($SQLITE_BUSY) so that's obviously the problem. The code is rather spread out, so I'll try to create a reduced test case and post it later today. Thanks! In the meantime, is there something obvious that I might have forgotten to do after my SELECTs? // EDIT: Fixed! I needed to add _SQLite_QueryFinalize() after my SELECTs. Edited November 17, 2006 by Stickman
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now