René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: remove the null prototype from result rows","articleBody":"**Current behavior**\n\nRows returned by `get()`, `all()` and `iterate()` are created with a `null` prototype. The V8 API that does this produces dictionary-mode objects, and V8 will not cache a prototype transition on a dictionary map, so every row also gets its own freshly allocated hidden class. Rows from the same statement therefore share no shape: they are slow to build, and every property access on them in user code is megamorphic.\n\n**Proposal**\n\nDrop the null prototype and build rows with `v8::DictionaryTemplate`, cached per statement. Rows become ordinary objects, and every row of a statement shares one hidden class.\n\n**Pros**\n\n- `all()` is 10–37% faster depending on the query; reading the rows afterwards is far cheaper still.\n- Consistent with `run()`, which already returns an ordinary object, and with `better-sqlite3`.\n\n**Cons**\n\n- Semver-major.\n- Rows can no longer be indexed by untrusted keys without `Object.hasOwn()` — `row.toString` and `row.constructor` start resolving through `Object.prototype`.\n- User code comparing rows against `{ __proto__: null, ... }` breaks.\n\nPrototype pollution is not a concern either way: rows are built by defining own properties directly, so a `__proto__` column is an own property and never reaches `Object.prototype`.\n\nI have benchmarks and a working implementation if there is interest.\n","author":{"url":"https://github.com/araujogui","@type":"Person","name":"araujogui"},"datePublished":"2026-09-04T17:45:47Z","url":"https://github.com/nodejs/node/issues/65799"}