René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: filter exception in `applyChangeset()` suppresses next SQLite error","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.5.2\n```\n\n### Subsystem\n\nsqlite\n\n### What steps will reproduce the bug?\n\n```js\nimport { DatabaseSync } from 'node:sqlite';\n\nconst source = new DatabaseSync(':memory:');\nconst target = new DatabaseSync(':memory:');\n\nsource.exec('CREATE TABLE t (id INTEGER PRIMARY KEY)');\ntarget.exec('CREATE TABLE t (id INTEGER PRIMARY KEY)');\n\nconst session = source.createSession();\nsource.exec('INSERT INTO t VALUES (1)');\n\ntry {\n  target.applyChangeset(session.changeset(), {\n    filter() {\n      throw new Error('filter failed');\n    },\n  });\n} catch (error) {\n  console.log('applyChangeset:', error.message);\n}\n\ntry {\n  const result = target.exec('invalid SQL');\n  console.log('invalid SQL:', result);\n} catch (error) {\n  console.log('invalid SQL threw:', error.message);\n}\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\n```console\napplyChangeset: filter failed\ninvalid SQL threw: near \"invalid\": syntax error\n```\n\nThe callback-failure state is cleared when `applyChangeset()` returns, so the invalid SQL throws an SQLite syntax error.\n\n### What do you see instead?\n\n```console\napplyChangeset: filter failed\ninvalid SQL: undefined\n```\n\nAfter catching the filter exception, unrelated invalid SQL silently returns `undefined`\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-29T15:06:29Z","url":"https://github.com/nodejs/node/issues/64822"}