Hi Nikki Many thanks for your answer. Its really helpful. First time it seems to me, that I understand the problem. In the past it happens, that the message in some Postings sometimes lives behind a Fog :-))) Thinks dont will be get clearly.
Its sometimes not so easy, to put it on the same line, what in the posting is written, and what the poster did mean. Sometimes it would be easier, if the answer to a question contains only a Yes or a No. In this case, I try to perform my question, that is a one of this possible... to hope, I can leave my helplessness... -------- Original-Nachricht -------- Datum: Wed, 05 Jul 2006 12:05:07 +0100 Von: Nikki Locke <[EMAIL PROTECTED]> An: sqlite-users@sqlite.org Betreff: Re: [sqlite] Multiple Users > ...the way SQLite works during a database update is that the > entire database file is locked, and remains locked until the update is > complete. If you use transactions, the entire database file is locked for > the entire transaction (*). It seems to me, that is (looked from the viewpoint "Frontend") another form of optimistic locking. I only have to look at the DB's busystate, until my changes are succesfully written to DB. > Provided you code handles the errors (by retrying the update until it > succeeds), it should work fine. Yep, it seems, that would solve my problems... Best greeetings from Germany ;-) Anne -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
