How does it handle SQLITE_BUSY error?

[pleerock]

How does it handle SQLITE_BUSY error? Can we handle it somehow properly to make first process to wait until another writes?

In node-sqlite3 there is an opened issue with handling sqlite busy error.

[mandaputtra]

If busy then you should maybe open the database with other app, and you forgot to save it.

Or maybe because sqlite not yet finish querying

[JoshuaWise]

When the database is busy, better-sqlite3 currently waits 5 seconds before allowing sqlite to throw a SQLITE_BUSY error. This value may be configurable in the future.

If you want to permit longer busy times, you could wrap your query in a try-catch-retry loop. However, it's more likely that you have some kind unintentional locking happening in your application (as @mandaputtra pointed out).

[JoshuaWise]

Here's an example of a try-catch-retry loop.

const db = require('better-sqlite3')('my-database.db');

const stmt = db.prepare(SQL);

while (true) {
  try {
    stmt.run();
    break;
  } catch (err) {
    if (err.code !== 'SQLITE_BUSY') throw err;
  }
}

[JoshuaWise]

As of version 5.0.0, there's now an option to specify a custom timeout, instead of the default 5 seconds. Read about it here.

[tintin10q]

For me I get the "This database connection is busy executing a query" error way before 5 seconds.

[titanism]

For me I get the "This database connection is busy executing a query" error way before 5 seconds.

same here, the timeout does not seem to be respected

edit: I'm using ava and it's using multiple processes/threads so that's probably culprit (ref: #1067)