Source Code: lib/sqlite.js
\nThe node:sqlite module facilitates working with SQLite databases.\nTo access it:
import sqlite from 'node:sqlite';\nconst sqlite = require('node:sqlite');\nThis module is only available under the node: scheme. The following will not\nwork:
import sqlite from 'sqlite';\nconst sqlite = require('sqlite');\nThe following example shows the basic usage of the node:sqlite module to open\nan in-memory database, write data to the database, and then read the data back.
import { DatabaseSync } from 'node:sqlite';\nconst database = new DatabaseSync(':memory:');\n\n// Execute SQL statements from strings.\ndatabase.exec(`\n CREATE TABLE data(\n key INTEGER PRIMARY KEY,\n value TEXT\n ) STRICT\n`);\n// Create a prepared statement to insert data into the database.\nconst insert = database.prepare('INSERT INTO data (key, value) VALUES (?, ?)');\n// Execute the prepared statement with bound values.\ninsert.run(1, 'hello');\ninsert.run(2, 'world');\n// Create a prepared statement to read data from the database.\nconst query = database.prepare('SELECT * FROM data ORDER BY key');\n// Execute the prepared statement and log the result set.\nconsole.log(query.all());\n// Prints: [ { key: 1, value: 'hello' }, { key: 2, value: 'world' } ]\n'use strict';\nconst { DatabaseSync } = require('node:sqlite');\nconst database = new DatabaseSync(':memory:');\n\n// Execute SQL statements from strings.\ndatabase.exec(`\n CREATE TABLE data(\n key INTEGER PRIMARY KEY,\n value TEXT\n ) STRICT\n`);\n// Create a prepared statement to insert data into the database.\nconst insert = database.prepare('INSERT INTO data (key, value) VALUES (?, ?)');\n// Execute the prepared statement with bound values.\ninsert.run(1, 'hello');\ninsert.run(2, 'world');\n// Create a prepared statement to read data from the database.\nconst query = database.prepare('SELECT * FROM data ORDER BY key');\n// Execute the prepared statement and log the result set.\nconsole.log(query.all());\n// Prints: [ { key: 1, value: 'hello' }, { key: 2, value: 'world' } ]\nThis class represents a single connection to a SQLite database. All APIs\nexposed by this class execute synchronously.
", "methods": [ { "textRaw": "`database.close()`", "type": "method", "name": "close", "meta": { "added": [ "v22.5.0" ], "changes": [] }, "signatures": [ { "params": [] } ], "desc": "Closes the database connection. An exception is thrown if the database is not\nopen. This method is a wrapper around sqlite3_close_v2().
This method allows one or more SQL statements to be executed without returning\nany results. This method is useful when executing SQL statements read from a\nfile. This method is a wrapper around sqlite3_exec().
Opens the database specified in the location argument of the DatabaseSync\nconstructor. This method should only be used when the database is not opened via\nthe constructor. An exception is thrown if the database is already open.
Compiles a SQL statement into a prepared statement. This method is a wrapper\naround sqlite3_prepare_v2().
Constructs a new DatabaseSync instance.
This class represents a single prepared statement. This class cannot be\ninstantiated via its constructor. Instead, instances are created via the\ndatabase.prepare() method. All APIs exposed by this class execute\nsynchronously.
A prepared statement is an efficient binary representation of the SQL used to\ncreate it. Prepared statements are parameterizable, and can be invoked multiple\ntimes with different bound values. Parameters also offer protection against\nSQL injection attacks. For these reasons, prepared statements are preferred\nover hand-crafted SQL strings when handling user input.
", "methods": [ { "textRaw": "`statement.all([namedParameters][, ...anonymousParameters])`", "type": "method", "name": "all", "meta": { "added": [ "v22.5.0" ], "changes": [] }, "signatures": [ { "return": { "textRaw": "Returns: {Array} An array of objects. Each object corresponds to a row returned by executing the prepared statement. The keys and values of each object correspond to the column names and values of the row.", "name": "return", "type": "Array", "desc": "An array of objects. Each object corresponds to a row returned by executing the prepared statement. The keys and values of each object correspond to the column names and values of the row." }, "params": [ { "textRaw": "`namedParameters` {Object} An optional object used to bind named parameters. The keys of this object are used to configure the mapping.", "name": "namedParameters", "type": "Object", "desc": "An optional object used to bind named parameters. The keys of this object are used to configure the mapping." }, { "textRaw": "`...anonymousParameters` {null|number|bigint|string|Buffer|Uint8Array} Zero or more values to bind to anonymous parameters.", "name": "...anonymousParameters", "type": "null|number|bigint|string|Buffer|Uint8Array", "desc": "Zero or more values to bind to anonymous parameters." } ] } ], "desc": "This method executes a prepared statement and returns all results as an array of\nobjects. If the prepared statement does not return any results, this method\nreturns an empty array. The prepared statement parameters are bound using\nthe values in namedParameters and anonymousParameters.
This method returns the source SQL of the prepared statement with parameter\nplaceholders replaced by values. This method is a wrapper around\nsqlite3_expanded_sql().
This method executes a prepared statement and returns the first result as an\nobject. If the prepared statement does not return any results, this method\nreturns undefined. The prepared statement parameters are bound using the\nvalues in namedParameters and anonymousParameters.
This method executes a prepared statement and returns an object summarizing the\nresulting changes. The prepared statement parameters are bound using the\nvalues in namedParameters and anonymousParameters.
The names of SQLite parameters begin with a prefix character. By default,\nnode:sqlite requires that this prefix character is present when binding\nparameters. However, with the exception of dollar sign character, these\nprefix characters also require extra quoting when used in object keys.
To improve ergonomics, this method can be used to also allow bare named\nparameters, which do not require the prefix character in JavaScript code. There\nare several caveats to be aware of when enabling bare named parameters:
\n$k and @k, in the same prepared\nstatement will result in an exception as it cannot be determined how to bind\na bare name.When reading from the database, SQLite INTEGERs are mapped to JavaScript\nnumbers by default. However, SQLite INTEGERs can store values larger than\nJavaScript numbers are capable of representing. In such cases, this method can\nbe used to read INTEGER data using JavaScript BigInts. This method has no\nimpact on database write operations where numbers and BigInts are both\nsupported at all times.
This method returns the source SQL of the prepared statement. This method is a\nwrapper around sqlite3_sql().
When Node.js writes to or reads from SQLite it is necessary to convert between\nJavaScript data types and SQLite's data types. Because JavaScript supports\nmore data types than SQLite, only a subset of JavaScript types are supported.\nAttempting to write an unsupported data type to SQLite will result in an\nexception.
\n| SQLite | \nJavaScript | \n
|---|---|
NULL | \nnull | \n
INTEGER | \nnumber or BigInt | \n
REAL | \nnumber | \n
TEXT | \nstring | \n
BLOB | \nUint8Array | \n