| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Signed-off-by: Guilherme Araújo <arauujogui@gmail.com>
|
Review requested:
|
Sorry, something went wrong.
Sorry, something went wrong.
|
@geeksilva97 are we good to land this? |
Sorry, something went wrong.
|
yes |
Sorry, something went wrong.
Commit Queue failed- Loading data for nodejs/node/pull/64219 ✔ Done loading data for nodejs/node/pull/64219 ----------------------------------- PR info ------------------------------------ Title sqlite: fix stale column count in StatementSync.all() (#64219) Author Guilherme Araújo <arauujogui@gmail.com> (@araujogui) Branch araujogui:sqlite-all-reprepare-num-cols -> nodejs:main Labels c++, author ready, commit-queue-squash, sqlite Commits 2 - sqlite: read column count after step in StatementSync.all() - sqlite: add schema-change regression tests Committers 1 - Guilherme Araújo <arauujogui@gmail.com> PR-URL: https://github.com/nodejs/node/pull/64219 Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/64219 Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> -------------------------------------------------------------------------------- ℹ This PR was created on Tue, 30 Jun 2026 18:02:50 GMT ✔ Approvals: 1 ✔ - Edy Silva (@geeksilva97): https://github.com/nodejs/node/pull/64219#pullrequestreview-4603550693 ✘ This PR needs to wait 22 more hours to land (or 0 minutes if there is one more approval) ✔ Last GitHub CI successful ℹ Last Full PR CI on 2026-07-01T11:39:39Z: https://ci.nodejs.org/job/node-test-pull-request/74486/ - Querying data for job/node-test-pull-request/74486/ ✔ Build data downloaded ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/28821161836 |
Sorry, something went wrong.
Signed-off-by: Guilherme Araújo <arauujogui@gmail.com> PR-URL: #64219 Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
SQLite 3.53.4 is a bug-fix release; its SHA3-256 was verified against the PRODUCT line on sqlite.org before pinning. The one node_sqlite.cc change upstream (nodejs/node#64219) defers sqlite3_column_count() until after the first step() in all(). Our port already resolves column metadata lazily on the first row, so it needed no equivalent change.
Signed-off-by: Guilherme Araújo <arauujogui@gmail.com> PR-URL: #64219 Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Signed-off-by: Guilherme Araújo <arauujogui@gmail.com> PR-URL: #64219 Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
If the schema changes after a statement is prepared, SQLite re-prepares it on the next sqlite3_step() call. StatementSync.prototype.all() reads the column count (sqlite3_column_count()) before that step, so on the first call after a schema change the count is stale.
StatementSync.prototype.get() is unaffected because it reads the count after stepping.