On 18/02/15 14:46, Richard Hipp wrote:
> I'm guessing that running "PRAGMA busy_timeout=4000;" (or some other
> reasonable number of milliseconds) shortly after opening the
> database connection will likely cure your problem.
> https://www.sqlite.org/pragma.html#pragma_busy_timeout You might
>
On 02/18/2015 06:53 AM, Tim Starling wrote:
> We (Wikimedia) are observing SQLITE_BUSY errors in our integration
> testing. The integration test consists of having a single browser
> instance view a MediaWiki site which uses SQLite 3.8 for its backend.
> The browser sends several parallel requests
We (Wikimedia) are observing SQLITE_BUSY errors in our integration
testing. The integration test consists of having a single browser
instance view a MediaWiki site which uses SQLite 3.8 for its backend.
The browser sends several parallel requests for CSS, JS, etc., and
MediaWiki writes to the
On 2/17/15, Tim Starling wrote:
> We (Wikimedia) are observing SQLITE_BUSY errors in our integration
> testing. The integration test consists of having a single browser
> instance view a MediaWiki site which uses SQLite 3.8 for its backend.
> The browser sends several parallel requests for CSS,
4 matches
Mail list logo