From 91aaf05a25ea22230daa7b777949006704c43b45 Mon Sep 17 00:00:00 2001 From: greenhead Date: Sat, 15 Aug 2026 23:41:37 +0900 Subject: [PATCH] doc: fix SQLite changeset constant descriptions Signed-off-by: greenhead PR-URL: https://github.com/nodejs/node/pull/65265 Refs: https://www.sqlite.org/session/c_changeset_abort.html Reviewed-By: Luigi Pinca Reviewed-By: James M Snell --- doc/api/sqlite.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/sqlite.md b/doc/api/sqlite.md index da7b4e12d8c..d05f817d75d 100644 --- a/doc/api/sqlite.md +++ b/doc/api/sqlite.md @@ -1675,11 +1675,11 @@ conflict resolution handler passed to [`database.applyChangeset()`][]. See also SQLITE_CHANGESET_CONSTRAINT - If foreign key handling is enabled, and applying a changeset leaves the database in a state containing foreign key violations, the conflict handler is invoked with this constant exactly once before the changeset is committed. If the conflict handler returns SQLITE_CHANGESET_OMIT, the changes, including those that caused the foreign key constraint violation, are committed. Or, if it returns SQLITE_CHANGESET_ABORT, the changeset is rolled back. + If any other constraint violation occurs while applying a change (i.e. a UNIQUE, CHECK or NOT NULL constraint), the conflict handler is invoked with this constant. SQLITE_CHANGESET_FOREIGN_KEY - If any other constraint violation occurs while applying a change (i.e. a UNIQUE, CHECK or NOT NULL constraint), the conflict handler is invoked with this constant. + If foreign key handling is enabled, and applying a changeset leaves the database in a state containing foreign key violations, the conflict handler is invoked with this constant exactly once before the changeset is committed. If the conflict handler returns SQLITE_CHANGESET_OMIT, the changes, including those that caused the foreign key constraint violation, are committed. Or, if it returns SQLITE_CHANGESET_ABORT, the changeset is rolled back.