v2.3.1

85612bf Minor performance optimization for Statement#each()
c7b5d38 Significant performance optimization for Statement#all()

v2.3.0

This release fixes a few minor bugs, significantly improves overall performance, and introduces the db.register() method, which allows you to define custom SQL functions.

0d4e336 added the db.register() method, allowing you to register custom SQL functions
f3daddb prepared statements and transactions can now be reused even after the table schema changes
6fff040 pluck() and safeIntegers() can no longer be invoked within an each() callback function

v2.2.0

ba97614 updated sqlite to 3.18.0
6b65dc3..1283e97 completely rewrote benchmarks
d2921ac minor performance improvement for .each()

v2.1.0

550fd8d added readonly mode via new Database(filename, {readonly: true})
404c739 improved performance of transaction objects

v2.0.0

5041cd8 updated copyright year
9588787 defaultSafeIntegers() now has the same semantics as safeIntegers()
59af62a removed event emitter from database prototype
0faf7a4 databases now open and close synchronously, instead requiring developers to use the event emitter interface

v1.4.0

852df57 added electron support

v1.3.9

4935a1e updated to sqlite3 3.15.0

v1.3.8

7dc4add Merge pull request #10 from bengotow/bengotow/ia32-support
f9969da fix support for ia32 on Windows

v1.3.6

29e04d6 added support for microsoft windows

v1.3.1

3779fc9 read-only statements that do not return data can now be executed with .run()

This removes the .readonly property and introduces the .returnsData property as its replacement. Statements are no longer semantically segregated based on whether they modify data, but rather whether they return data. There are two major reasons for this:

• It makes more sense to .prepare('BEGIN;').run() than to .prepare('BEGIN;').get()
• Both CREATE TABLE foo (bar) and CREATE TABLE IF NOT EXISTS foo (bar) should use the same execution method (.run())