"=?ISO-8859-1?Q?Edwin_Hern=E1n_Barrios_N=FA=F1ez?=" <[EMAIL PROTECTED]> wrote: > Hi everybody > > this is my fist message on this list. > > Well, i know that my subject sounds a little stupid, by the way > sqlite3 evolution trys to performe better ACID. But i want to force > blocking the db file while my aplication is running. > I'm using sqlite for session cache, i don't want that a user change > my sqlite db with other instance of my app, or using sqlite command > line. > > On this moment i'm using "begin exclusive", to block. The real problem > is that my aplication is a GUI aplication and y use the event loop to > notify errors; when an error occurs sqlite3 end my transaction then by > a litle interval of time the db is unblocked before my error event > recreate the exclusive transaction.
What kind of error is closing your transaction? When SQLite hits an error, it usually leaves the transaction open. -- D. Richard Hipp <[EMAIL PROTECTED]>
