		@@ -11,5 +11,10 @@ 'use strict';

		process.on('SIGINT', function () {fs.removeSync('temp/'); process.exit();});
		process.on('SIGHUP', function () {fs.removeSync('temp/'); process.exit();});
		process.on('SIGTERM', function () {fs.removeSync('temp/'); process.exit();});

		var trials = fs.readdirSync(path.join(__dirname, 'trials')).filter(function (name) {return name[0] !== '.';});
		if (!trials.length) {
		console.log(clc.yellow('No benchmarks exist!'));
		fs.removeSync('temp/');
		process.exit();
		@@ -46,4 +51,4 @@ }
		if (!trials.length) {
		console.log(clc.green('All benchmarks complete!'));
		fs.removeSync('temp/');
		console.log(clc.green('All benchmarks complete!'));
		process.exit();
		@@ -50,0 +55,0 @@ }

benchmark/trials/insert.wal.small.js

+@@ -6,3 +6,3 @@ 'use strict';
+	theirDb.exec('PRAGMA journal_mode = WAL; PRAGMA synchronous = 1;', function () {
+		require('../insert-trial')(ourDb, theirDb, 500, [
+		require('../insert-trial')(ourDb, theirDb, 5000, [
+			'John Smith',
+@@ -9,0 +9,0 @@ 123456,

package.json

		{
		"name": "better-sqlite3",
		"version": "0.9.1",
		"version": "0.9.2",
		"description": "The fastest and most carefully designed library for SQLite3 in Node.js.",
		@@ -5,0 +5,0 @@ "homepage": "http://github.com/JoshuaWise/better-sqlite3",

README.md

		@@ -1,2 +0,2 @@
		# better-sqlite3
		# better-sqlite3 [![Build Status](https://travis-ci.org/JoshuaWise/better-sqlite3.svg?branch=master)](https://travis-ci.org/JoshuaWise/better-sqlite3)

		@@ -6,5 +6,5 @@ The fastest and most carefully designed library for SQLite3 in Node.js.
		- Full transaction support
		- Full atomicity on a single connection
		- Geared for performance and efficiency
		- Easy-to-use node-style API
		- Idiomatic node-style API
		- Includes convenient time-saving utilities

		@@ -34,3 +34,3 @@ ## Installation
		- `node-sqlite3` exposes low-level (C language) memory management functions. `better-sqlite3` does it the JavaScript way, allowing the garbage collector to worry about memory management.
		- This module secretly splits your database connectino into two parts; a read-only connection, and a writable connection, which gives you completely atomic transactions and protects you from reading uncommitted data.
		- `better-sqlite3` is just as fast, (even faster in some cases) than `node-sqlite3`.

		@@ -70,4 +70,2 @@ # API

		#### WARNING: You should NOT use prepared [statements](#statementstring---statement) or [transactions](#transactionarrayofstrings---transaction) to run PRAGMA statements. Doing so could result in database corruption.

		### .checkpoint([force], callback) -> this
		@@ -235,3 +233,3 @@

		By default, SQLite3 databases are not well suited for some write-heavy applications. If your application reads frequently, but writes to the database very infrequently, you'll probably be fine. But if this is not the case, it's recommended to turn on [WAL mode](https://www.sqlite.org/wal.html):
		Concurrently reading and writing from an SQLite3 database can be very slow in some cases. Since concurrency is usually very important in web applications, it's recommended to turn on [WAL mode](https://www.sqlite.org/wal.html) to greatly increase overall performance and concurrency.

		@@ -238,0 +236,0 @@ ```js

src/objects/statement/busy.cc

.travis.yml