Re: [sqlite] Database locking issue
Hi, now I have tried the actual version 3.6.3 as of sqlite- amalgamation-3.6.3.tgz, but still get database locks I cannot explain. Brief information: I use two database files. One (lbDMF.db3) for system informations such as what my application should show in forms of a database (Template Designer.db3). The system database therefore is required to store sql queries of the application database (Template Designer.db3). Looking at the files after I have the lock situation (after a successfull close I also get a lock when reopened) I have determined content in Template Designer.db3-journal that shows words (of columns or tables from lbDMF.db3. How could it be, that there is content in that file that fas nothing to do with that database ? Here is the content: Ÿ’˘ °c◊öà ts/CPP/Test/GUI/wxWrapper/Template Designer .db3 ö Ö V 8 ¸ › æ ü Å c E . ‡ ¿ †åxdJ0 Ú Œ ™ ã l M 3 IdAnwendungsparameter! 3 idAnwendungsparameter 3 IDAnwendungsparameter = IdFormularaktionenzuordnen = idFormularaktionenzuordnen = IDFormularaktionenzuordnen ) IdUebersetzungen ) idUebersetzungen ) IDUebersetzungen IdAktionen idAktionen IDAktionen 5 IdAnwendungenFormulare ú Ïÿƒ∞ú LiliLili Lili LuluLulu Lulu LoloLolo Lolo LalaLala Lala TestTest Testöà The words Anwendungsparameter, Formularaktionenzuordnen, Uebersetzungen, Aktionen and AnwendungenFormulare are columns or tables from lbDMF. I am confused !! Also I could rename these files while the application claims they are locked. (This happens while an update attempt I'll give a retry with a shortly closed database to get rid of the lock, but the lock remains) Any hints are welcome. Thanks, Lothar Am 19.09.2008 um 17:37 schrieb Lothar Behrens: Am 19.09.2008 um 17:03 schrieb Ken: Try it with the latest full build say version 3.6.2 and see what happens instead of a patched I'll give that a try. Could the current code be compiled with Open Watcom as A DLL ? (I haven't seen these __declspec(dllexport) and the opposite stuff in the actual code) Lothar -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Database locking issue
Hi, I am using Version 3.5.2 of Sqlite with the changes of the following CVS checkin numbers: 4543 and 5243 to get the sqlite3_sql and sqlite3_next_stmt functions into my API. I have patched my files due to the need to figuring out what statements were unfinalized. But now I get 'database is locked' errors right after reopening the database (the closing of the database works as I try to keep my statements open as short as possible thus closing now works). Due to this new error ('database is locked') I added reporting statemens in use. The result of this is a report of the insert statement itself that causes the error for this report. So I am a little confused. If a database is locked, is there always a statement that causes this lock, or is the lock keeping even the statement gets finalized ? Or did I have to apply other patches related to them above ? Thanks Lothar -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Database locking issue
Try it with the latest full build say version 3.6.2 and see what happens instead of a patched --- On Fri, 9/19/08, Lothar Behrens [EMAIL PROTECTED] wrote: From: Lothar Behrens [EMAIL PROTECTED] Subject: [sqlite] Database locking issue To: General Discussion of SQLite Database sqlite-users@sqlite.org Date: Friday, September 19, 2008, 9:02 AM Hi, I am using Version 3.5.2 of Sqlite with the changes of the following CVS checkin numbers: 4543 and 5243 to get the sqlite3_sql and sqlite3_next_stmt functions into my API. I have patched my files due to the need to figuring out what statements were unfinalized. But now I get 'database is locked' errors right after reopening the database (the closing of the database works as I try to keep my statements open as short as possible thus closing now works). Due to this new error ('database is locked') I added reporting statemens in use. The result of this is a report of the insert statement itself that causes the error for this report. So I am a little confused. If a database is locked, is there always a statement that causes this lock, or is the lock keeping even the statement gets finalized ? Or did I have to apply other patches related to them above ? Thanks Lothar -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Database locking issue
Am 19.09.2008 um 17:03 schrieb Ken: Try it with the latest full build say version 3.6.2 and see what happens instead of a patched I'll give that a try. Could the current code be compiled with Open Watcom as A DLL ? (I haven't seen these __declspec(dllexport) and the opposite stuff in the actual code) Lothar -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de Lothar Behrens Heinrich-Scheufelen-Platz 2 73252 Lenningen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users