Julien Sobrier wrote: > Joshua Tauberer wrote: >> Hi, >> >> The only change between 1.1.13 and 1.1.14, as far as I can see/remember, >> is the addition of a new busy_timeout parameter in the connection >> string. If you haven't set that, 1.1.13 and 1.1.14 should behave >> identically. (And, OTOH, setting that parameter might help you avoid >> those exceptions. I see it's not documented on the wiki, so I'll add >> that now.) >> > > Thank, I saw the busy_timeout parameter on the web site. But I have a > question about how it works exactly: the query will be run again after > the time defined in busy_timeout, it will be run several times until the > base is unlocked or we exceed the timeout, what ever comes first?
Yeah, the latter. It's implemented as a call to sqlite(3)_busy_timeout: http://sqlite.org/capi3ref.html#sqlite3_busy_timeout -- - Joshua Tauberer http://taubz.for.net "Unfortunately, we're having this discussion. It's too bad, because guess who listens to the discussion: the enemy." _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
