RE: [sqlite] Locking in 3.0.5
>>So, Rob, are you go to tell us if you think the change >>is an improvement or not? It seems that with either of the new schemes, when using sqlite3_busy_timeout() one thread is going to timeout sooner or later. That being the case I prefer the new version on efficiency grounds. Being a lazy programmer, I like the behaviour of 2.8.15 where both threads can get to complete their update, timeouts allowing. This is behaviour that I am also used to with MS SQL Server. I agree with you that many programmers (myself included) don't want to have to worry about this stuff too much when using SQLite. Rob.
RE: [sqlite] Locking in 3.0.5
I have just read the archive mailing list from 16/08/2004, and it looks like this behaviour is on purpose (checkin 1879). My mistake, Rob. -Original Message- From: Rob Groves [mailto:[EMAIL PROTECTED] Sent: 31 August 2004 22:17 To: [EMAIL PROTECTED] Subject: [sqlite] Locking in 3.0.5 Hi, I have observed different behaviour between 3.0.3 and 3.0.5. I didn't download 3.0.4 so can't comment on that. I am using two threads and setting a busy timeout on each with sqlite3_busy_timeout(). In 3.0.3 two threads trying to update the same row(s) would both retry until the one with the shortest busy timeout expired, and SQLITE_BUSY is returned. In 3.0.5, the 2nd thread trying to obtain the lock returns SQLITE_BUSY immediately. Any ideas? Rob.
[sqlite] Locking in 3.0.5
Hi, I have observed different behaviour between 3.0.3 and 3.0.5. I didn't download 3.0.4 so can't comment on that. I am using two threads and setting a busy timeout on each with sqlite3_busy_timeout(). In 3.0.3 two threads trying to update the same row(s) would both retry until the one with the shortest busy timeout expired, and SQLITE_BUSY is returned. In 3.0.5, the 2nd thread trying to obtain the lock returns SQLITE_BUSY immediately. Any ideas? Rob.
RE: [sqlite] Newbie questions
>>The sqlite_compile/step/finalize paradigm allows (requires really ) >>forward browsing through a result set. The results from sqlite_get_table() allow random access, should this be required, and I have even had success using qsort() on the results to re-order them without needing to re-query the database. That reminds me, does anybody know if sqlite_get_table() is supported in version 3.0? Rob. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [sqlite] the second argument of sqlite_open
> Will the [SQLite 3] API change much? What do you think -> do we need to rewrite much code > if we use the function with the callback method? >From what I can see, the SQLite 3 proposal does not commit to keeping the sqlite_exec() function. >>If you want to move to version 3, the API will >>be very similar, but there will be a few differences. >>You will not need to change much code, I don't think, >>to move from version 2 to version 3. Christian may want to look at CppSQLite. I plan to make a version available for SQLite 3, and from what I can see so far, the new API will be an excellent fit with the existing CppSQLite classes, which I hope to keep compatible with existing CppSQLite when the time comes. Cheers, Rob. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [sqlite] CppSQLite
>>There is no copyright statement or license stated in the article >>or in the download. >>So it isn't clear what the legal status is of CppSQLite? There is a copyright notice at the end of every CodeProject article. However, I now intend to add a BSD style licence to all the source code files. Thanks, Rob. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sqlite] CppSQLite
For those that are interested, a new version of CppSQLite and accompanying article is available here: http://www.codeproject.com/database/CppSQLite.asp Main new features are support for pre-compiled SQL and multithreaded features of SQLite, plus removal of Microsoft specific C++. Cheers, Rob.
[sqlite] sqlite_compile() different behaviour in 2.8.12 and 2.8.13
Hi all, I'm working on an update to CppSQLite. I have noticed that in 2.8.13 sqlite_compile() can return SQLITE_BUSY. In 2.8.12 I only ever saw SQLITE_BUSY come from sqlite_finalize() after sqlite_step() had failed. In 2.8.13 it seems it can come from either. This is not a problem, but what is the intended behaviour? Cheers, Rob Groves Author of CppSQLite http://www.codeproject.com/database/CppSQLite.asp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
