sqlite: rename DatabaseSync and StatementSync

Rename the DatabaseSync and StatementSync classes to Database and
Statement, and the internal DatabaseSyncLimits helper to
DatabaseLimits. The old names are kept as aliases of the new classes
and are Documentation-only deprecated (DEP0210, DEP0211).

Assisted-by: Claude Code
Signed-off-by: Guilherme Araújo <arauujogui@gmail.com>
PR-URL: #65988
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Gürgün Dayıoğlu <hey@gurgun.day>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

Author: araujogui

SECURITY.md

@@ -430,14 +430,14 @@ the community they pose.
 
 * Examples of scenarios that are **not** Node.js vulnerabilities:
   * Allowing untrusted users to register SQLite user-defined functions via
-    `node:sqlite` (`DatabaseSync`) that can perform arbitrary operations
+    `node:sqlite` (`Database`) that can perform arbitrary operations
     (e.g., closing database connections during query execution, causing crashes
     or use-after-free conditions).
   * Loading SQLite extensions using the `allowExtension` option in
-    `DatabaseSync` — this option must be explicitly set to `true` by the
+    `Database` — this option must be explicitly set to `true` by the
     application, and enabling it is the application operator's responsibility.
   * Using `node:sqlite` built-in SQL functions or pragmas (e.g.,
-    `ATTACH DATABASE`) to read or write files — `DatabaseSync` operates with
+    `ATTACH DATABASE`) to read or write files — `Database` operates with
     the same file-system access as the process itself, and it is the
     application's responsibility to restrict what SQL is executed.
   * Exposing `child_process.exec()` or similar APIs to untrusted users without
@@ -532,7 +532,7 @@ The following are **not** vulnerabilities in Node.js:
   access. Inconsistent checks on these paths are treated as regular bugs and
   should be reported through the public issue tracker.
 
-* **`node:sqlite` and the permission model**: `DatabaseSync` operates with the
+* **`node:sqlite` and the permission model**: `Database` operates with the
   same file-system privileges as the process. Using SQL pragmas or built-in
   SQLite mechanisms (e.g., `ATTACH DATABASE`) to access files does not bypass
   the permission model — the permission model does not intercept SQL-level

benchmark/sqlite/sqlite-diagnostic-channel.js

@@ -12,7 +12,7 @@ const bench = common.createBenchmark(main, {
 function main(conf) {
   const { n, mode } = conf;
 
-  const db = new sqlite.DatabaseSync(':memory:');
+  const db = new sqlite.Database(':memory:');
   db.exec('CREATE TABLE t (x INTEGER)');
   const insert = db.prepare('INSERT INTO t VALUES (?)');
 

benchmark/sqlite/sqlite-is-transaction.js

@@ -9,7 +9,7 @@ const bench = common.createBenchmark(main, {
 });
 
 function main(conf) {
-  const db = new sqlite.DatabaseSync(':memory:');
+  const db = new sqlite.Database(':memory:');
 
   if (conf.transaction === 'true') {
     db.exec('BEGIN');

benchmark/sqlite/sqlite-prepare-insert.js

@@ -17,7 +17,7 @@ const bench = common.createBenchmark(main, {
 });
 
 function main(conf) {
-  const db = new sqlite.DatabaseSync(':memory:');
+  const db = new sqlite.Database(':memory:');
 
   db.exec('CREATE TABLE text_column_type (text_column TEXT)');
   db.exec('CREATE TABLE integer_column_type (integer_column INTEGER)');

benchmark/sqlite/sqlite-prepare-select-all-options.js

@@ -19,7 +19,7 @@ function main(conf) {
     return acc;
   }, {});
 
-  const db = new sqlite.DatabaseSync(':memory:', optionsObj);
+  const db = new sqlite.Database(':memory:', optionsObj);
 
   db.exec(
     'CREATE TABLE foo (text_column TEXT, integer_column INTEGER, real_column REAL, blob_column BLOB)',

benchmark/sqlite/sqlite-prepare-select-all.js

@@ -24,7 +24,7 @@ const bench = common.createBenchmark(main, {
 });
 
 function main(conf) {
-  const db = new sqlite.DatabaseSync(':memory:');
+  const db = new sqlite.Database(':memory:');
 
   // Create only the necessary table for the benchmark type.
   // If the statement includes 'foo_large', create the foo_large table; otherwise, create the foo table.

benchmark/sqlite/sqlite-prepare-select-get-options.js

@@ -18,7 +18,7 @@ function main(conf) {
     return acc;
   }, {});
 
-  const db = new sqlite.DatabaseSync(':memory:', optionsObj);
+  const db = new sqlite.Database(':memory:', optionsObj);
 
   db.exec(
     'CREATE TABLE foo (text_column TEXT, integer_column INTEGER, real_column REAL, blob_column BLOB)',

benchmark/sqlite/sqlite-prepare-select-get.js

@@ -18,7 +18,7 @@ const bench = common.createBenchmark(main, {
 });
 
 function main(conf) {
-  const db = new sqlite.DatabaseSync(':memory:');
+  const db = new sqlite.Database(':memory:');
 
   // Create only the necessary table for the benchmark type.
   // If the statement includes 'foo_large', create the foo_large table; otherwise, create the foo table.

doc/api/deprecations.md

@@ -4710,6 +4710,34 @@ async function example() {
 }
 ```
 
+### DEP0210: `sqlite.DatabaseSync`
+
+<!-- YAML
+changes:
+  - version: REPLACEME
+    pr-url: https://github.com/nodejs/node/pull/65988
+    description: Documentation-only deprecation.
+-->
+
+Type: Documentation-only
+
+`node:sqlite`'s `DatabaseSync` class was renamed to `Database`. `DatabaseSync`
+is kept as a deprecated alias. Use `Database` instead.
+
+### DEP0211: `sqlite.StatementSync`
+
+<!-- YAML
+changes:
+  - version: REPLACEME
+    pr-url: https://github.com/nodejs/node/pull/65988
+    description: Documentation-only deprecation.
+-->
+
+Type: Documentation-only
+
+`node:sqlite`'s `StatementSync` class was renamed to `Statement`.
+`StatementSync` is kept as a deprecated alias. Use `Statement` instead.
+
 [DEP0142]: #dep0142-repl_builtinlibs
 [NIST SP 800-38D]: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf
 [RFC 6066]: https://tools.ietf.org/html/rfc6066#section-3

doc/api/diagnostics_channel.md

@@ -2001,14 +2001,14 @@ added: v26.8.0
 * `sql` {string} The expanded SQL with bound parameter values substituted.
   If expansion fails, the source SQL with unsubstituted placeholders is used
   instead.
-* `database` {DatabaseSync} The [`DatabaseSync`][] instance that executed the
+* `database` {Database} The [`Database`][] instance that executed the
   statement.
 * `duration` {number} SQLite's internal estimate of the statement run time in
   nanoseconds. This reflects C-layer execution time only and does not include
   JavaScript binding overhead such as argument marshaling or result-row
   construction.
 
-Emitted after a SQL statement finishes executing against a [`DatabaseSync`][]
+Emitted after a SQL statement finishes executing against a [`Database`][]
 instance. This is a **profiling** event: it fires once per statement upon
 completion and reports an estimated duration from SQLite's internal profiler.
 It is not a distributed-tracing span. There is no corresponding start event,
@@ -2030,7 +2030,7 @@ statement, since both are still in use while the event is being delivered; see
 [`--enable-fips-indicator-events`]: cli.md#--enable-fips-indicator-events
 [`--force-fips=strict`]: cli.md#--force-fips
 [`BoundedChannel`]: #class-boundedchannel
-[`DatabaseSync`]: sqlite.md#class-databasesync
+[`Database`]: sqlite.md#class-database
 [`TracingChannel`]: #class-tracingchannel
 [`asyncEnd` event]: #asyncendevent
 [`asyncStart` event]: #asyncstartevent