René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: StatementSync.run() loses precision for lastInsertRowid instead of throwing ERR_OUT_OF_RANGE","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.6.0\n```\n\n### Subsystem\n\nsqlite\n\n### What steps will reproduce the bug?\n\n```js\nimport { DatabaseSync } from 'node:sqlite';\n\nconst db = new DatabaseSync(':memory:');\ndb.exec('CREATE TABLE t (id INTEGER PRIMARY KEY)');\n\nconst result = db\n  .prepare('INSERT INTO t VALUES (?)')\n  .run(9007199254740993n);\n\nconsole.log(result);\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\nIt should use the documented integer-conversion behavior: throw `ERR_OUT_OF_RANGE` by default\n\nIt should return a `BigInt` when BigInt reading is enabled.\n\n### What do you see instead?\n\n```console\n{ changes: 1, lastInsertRowid: 9007199254740992 }\n```\n\n`sqlite3_last_insert_rowid()` returns the correct 64-bit integer, but `StatementSync.run()` converts it directly to a JavaScript `Number`, silently rounding values beyond the safe-integer range.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-08-10T03:47:19Z","url":"https://github.com/nodejs/node/issues/65177"}