Hello :-) I'm the student who develop the new SQLite-Driver.
> I will bet the confusion is with the BEGIN variations. No, there isn't a problem with the Transaction-Locks. [1] The 'problem' is that SQLite locks the complete database if you have a SELECT-Query running with sqlite3_step(). In that time you can't change anything in the database as long as the sqlite3_stmt* query is not reset() or finalized()! A user of OOo can have more than one window on his desktop and OOo don't close querys if they are still needed in resultset. So the database is locked because of a simple SELECT-Query. If the user wants to create a new table or insert/update a row, it will fail. But the problem is fixed in next version of my driver. I will use temporary tables to have an opened resultset that don't lock the database-file. (see SQLite: CREATE TEMP TABLE) But I think that problem will be fixed in SQLite soon. [2] The current source in CVS isn't usable in productive environment at the moment. :-) But I will continue working on it after Sommer of Code. [1] http://www.sqlite.org/lang_transaction.html [2] http://www.sqlite.org/cvstrac/chngview?cn=3355 Regards, André Klitzing --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
