Joe Wilson wrote: > --- Bill KING <[EMAIL PROTECTED]> wrote: > >> Outside of, and I use Qt's QReadWriteLock. ->lockForRead()/lockForWrite() >> http://doc.trolltech.com/4.1/qreadwritelock.html >> > > Thanks. > > Many follow-up questions... :-) > > Is this for an application or for the Qt SQLite database driver class? > If it is the latter, how could your database wrapper code know when > to employ a read lock vs. write lock? Only transactions use write locks? > What about a standalone update, insert or delete outside a transaction? > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > This is for essentially a standalone ;) I'm in the Mobile and Embedded Systems office, working on QTopia (mobile phone/pda/portable media player operating environment). Essentially, this is the backend engine for a document management system, so I control all access to this particular database via an engine interface class, which in turn means that I can read or write lock around each QSqlQuery as fits.
http://doc.trolltech.com/qtopia4.1/docsys-overview.html The documentation at the link above is a little out of date, but gives a good idea/overview. -- Bill King, Software Engineer Trolltech, Brisbane Technology Park 26 Brandl St, Eight Mile Plains, QLD, Australia, 4113 Tel + 61 7 3219 9906 (x137) Fax + 61 7 3219 9938 mobile: 0423 532 733
