Please report any issues on GitHub
For this module to work, you need a version of the sqlite3 command line tool installed on your system. Many versions will work, however, it is strongly recommended that you install version 3.33.0 or above as this provides native JSON support. Versions below 3.33.0 will use HTML output as an alternative.
Caveat: if you use an older version, all columns will be returned as strings by default. Please look at the
autoConvertoption to change that behavior
This module allows you to interact with the sqlite3 binary installed on your system to access SQLite databases. It is 100% JavaScript. This will entirely alleviate binary dependencies such as for the sqlite3 and better-sqlite modules.
Caveat: Beware that, unlike with sqlite3, you do not have a connection to the database by creating a
Databaseobject! Transactions must be run in a singlerun()orexec()command! Every query you run will be automatically preceded byPRAGMAcommands to set busy timeout and enable foreign keys.
Inserting large numbers of records should always be done inside of a transaction in sqlite3 to help with performance:
BEGIN TRANACTION;
INSERT INTO table (field, field, ..) VALUES
(a, b, c, ...),
(d, e, f, ...)
....
(z, z, z, ...);
COMMIT;A test inserting 15000 records took 258 ms, so around 58000 records/s.
Inserting those same 15000 records and reading them back took 272 ms for JSON support and 370 ms for HTML.
npm:
npm install noarch-sqlite3yarn:
yarn add noarch-sqlite3Here is a very straightforward example of how to use noarch-sqlite3:
const { Database } = require('noarch-sqlite3');
const options = { busyTimeout: 20000 };
const db = new Database('./mydb.db3', options);
// Callback style
db.all('SELECT * FROM table', (err, records) =>
{
if (err)
{
console.error(err.message);
return;
}
console.log(records);
});
// Promise style
async function run()
{
const records = await db.all('SELECT * FROM table');
console.log(records);
}
run()
.catch(err => console.log(err.message));All functions allow you to use either Promise-style calling or callback-style. You cannot mix the two styles. If you use callback-style, many functions will return the Database object to allow for function chaining. In case of Promise-style, that will not be available.
The API is mostly identical to that of the sqlite3 package and its API.
☝️ this module allows you to use Promise-style calling, which is not available in the sqlite3 package.
Return a new Database object. This will use the executable set by the sqlite3Path option to determine your current sqlite3 command line version. It will detect whether JSON is supported (Database.useJson).
-
filename: The name of your new or already existing sqlite3 database -
options(optional) Object containing valid option properties.Options can be one of the following:
-
autoConvert: instead of the default behavior of returning all values as strings, auto-convert 'true' and 'false' to their boolean values and '1'/'1.1' to their numeric values (only applies to pre-3.33.0 versions ofsqlite3) -
busyTimeout: allows you to override the default busy timeout of 30000 ms -
enableForeignKeys: allows you to override enforcements of foreign keys (default: true) -
outputBufferSize: allows you to override the maximum output buffer size for large query results (default: 1024 * 1024) -
sqlite3Path: full path of thesqlite3executable. Allows you to override the default location (/usr/bin/sqlite3)
-
May throw:
- sqlite3 executable not found
- unable to determine sqlite3 version
- invalid (non semver) sqlite3 version detected
- more recent version of sqlite3 required
Fake close that is only there to provide drop-in compatibility with sqlite3
callback(optional): called immediately withnull
Set a configuration option for the database.
Run all (semicolon separated) SQL queries in the supplied string. No result rows are retrieved. If the callback parameter is present, this will return the Database object to allow for function chaining. If present, on completion or failure, the callback will be called with either null or an Error object as its only argument. If no callback is present, the function will return a Promise that will resolve on success or reject on failure.
-
sql: The SQL query to run. -
param, ...(optional): If the SQL statement contains placeholders, parameters passed here will be replaced in the statement before it is executed. This automatically sanitizes inputs.There are three ways of passing bind parameters: directly in the function's arguments, as an array or as an object. Parameters may not be used for column or table names.
// Directly in the function arguments. db.run("UPDATE tbl SET name = ? WHERE id = ?", "bar", 2); // As an array. db.run("UPDATE tbl SET name = ? WHERE id = ?", [ "bar", 2 ]); // As an object. db.run("UPDATE tbl SET name = $name WHERE id = $id", { name: "bar", id: 2 }); db.run("UPDATE tbl SET name = :name WHERE id = :id", { name: "bar", id: 2 }); db.run("UPDATE tbl SET name = @name WHERE id = @id", { name: "bar", id: 2 }); // As an object with [sqlite3] compatibility db.run("UPDATE tbl SET name = $name WHERE id = $id", { $name: "bar", $id: 2 }); db.run("UPDATE tbl SET name = :name WHERE id = :id", { ":name": "bar", ":id": 2 }); db.run("UPDATE tbl SET name = @name WHERE id = @id", { "@name": "bar", "@id": 2 });The sqlite3 module that this API is mostly based on, requires that the placeholders in the query strictly match the fields in the object.
In case you want to keep the callback as the 3rd parameter, you should set
paramto[](empty Array),{}(empty object) orundefinedYou can use either an array or object or pass each parameter as an argument. Do not mix those!
-
callback(err)(optional): Will be called if anErrorobject if any error occurs during execution.
Run the SQL query with the specified parameters and call the callback with all result rows afterwards. If the callback parameter is present, this will return the Database object to allow for function chaining. If no callback is present, the function will return a Promise that will resolve on success or reject on failure. The parameters are the same as the Database#run function, with the following differences:
The signature of the callback is: function(err, rows) {}. rows is an array. If the result set is empty, it will be an empty array, otherwise it will have an object for each result row which in turn contains the values of that row, like the Database#get function.
All result rows are retrieved first and stored in memory!
Please note that, while this function allows query to contain multiple semicolon separated SQL statements, the result can get highly confusing if any of the queries do not return results. You will get a set of records back:
[
[ records for query 1],
[ records for query 2]
...
]
However, any query that does not return anything will not have an empty entry in the set. Moreover, if there is only one set of records present, only that set is returned:
[ record for set with result ]
In that case you will not receive an array of arrays!
Run the SQL query with the specified parameters and call the callback once for each result row. If the callback parameter is present, this will return the Database object to allow for function chaining. If no callback is present, the function will return a Promise that will resolve on success or reject on failure. The parameters are the same as the Database#run function, with the following differences:
The signature of the callback is: function(err, row) {}. If the result set succeeds but is empty, the callback is never called. In all other cases, the callback is called once for every retrieved row. The order of calls correspond exactly to the order of rows in the result set.
After all row callbacks were called, the completion callback will be called if present. The first argument is an error object, and the second argument is the number of retrieved rows. If you specify only one function, it will be treated as row callback, if you specify two, the first (== second to last) function will be the row callback, the last function will be the completion callback.
This function (currently) loads all rows in memory first!
This is an alias for Database#run
Run the SQL query with the specified parameters and call the callback with a subsequent result row. If the callback parameter is present, this will return the Database object to allow for function chaining. If no callback is present, the function will return a Promise that will resolve on success or reject on failure. The parameters are the same as the Database#run function, with the following differences:
The signature of callback is: function(err, row) {}. If the result set is empty, the row parameter is undefined, otherwise it is an object containing the values for the first row.
Run multiple queries in succession. If the callback parameter is present, this will return the Database object to allow for function chaining. If present, on completion or failure, the callback will be called with either null or an Error object as its only argument. If no callback is present, the function will return a Promise that will resolve on success or reject on failure.
The queries will be run in exactly the order in which they are found in the array
-
queries: The SQL queries to run. This is an array of sets of arguments like you would pass to Database#run:db.runAll([ [ "INSERT INTO table (name) VALUES (?)", "one" ], [ "INSERT INTO table (name) VALUES (?)", "two" ] ], err => console.log(err)); )If you want to pass plain queries without placeholders, you can pass them as strings or even mix both forms;
db.runAll([ "INSERT INTO table (name) VALUES ('one')", [ "INSERT INTO table (name) VALUES (?)", "two" ], "INSERT INTO table (name) VALUES ('three')", [ "INSERT INTO table (name) VALUES (?)", [ "four" ] ] ], err => console.log(err)); ) -
callback(err)(optional): Will be called if anErrorobject if any error occurs during execution.
Return an object describing the version of sqlite3 found in the sqlite3Path on your system. For example:
{
version: "3.37.0",
data: "2021-12-09 01:34:53",
hash: "9ff244ce0739f8ee52a3e9671adb4ee54c83c640b02e3f9d185fd2f9a179aapl"
}Includes debug support for the main module as well as the sqlite3parse module:
DEBUG="noarch-sqlite3,sqlite3parse" node my-code.js
Please check the extended changelog (GitHub)