Nice analogy, but in the case the cat really does have 9 lives (or many more) 'cause with SQLITE_BUSY you can just retry and while retrying is a performance penalty in my experience SQLITE_BUSY is a very rare occurrence.
All I'm saying is don't fix a perceived problem until you've tested to be sure your perception is correct. Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Friday, June 01, 2007 9:40 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Concurrency You make a very good point. Someone called it the "cat running over the road" situation. A cat runs across a busy road without looking by going as fast as possible and rarely does one get run over. On the other hand roads are lined with dead armadillos. If you synchronization logic is sound and you avoid polling or waits the faster your database runs the more concurrent transactions per second you will achieve. ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
