-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
sqlite: statement.setReadNullAsUndefined() #59462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jac0bandres
wants to merge
6
commits into
nodejs:main
Choose a base branch
from
jac0bandres:dev
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+262
−20
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1c3702c
src: add setReadNullAsUndefined() to StatementSync in node_sqlite.cc …
jac0bandres f4a6327
Merge branch 'nodejs:main' into dev
jac0bandres 06e050f
sqlite: add statement.setReadNullAsUndefined, add options.readNullAsU…
jac0bandres 8af485a
sqlite: add statement.setReadNullAsUndefined, add options.readNullAsU…
jac0bandres f248a9e
sqlite: add statement.setReadNullAsUndefined, add options.readNullAsU…
jac0bandres b62aed9
sqlite: add statement.setReadNullAsUndefined, add options.readNullAsU…
jac0bandres File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LiviaMedeiros when the value is undefined, should it be included as a key in the returned object?
V8 optimizes creation of the objects with similar shape but I don't know if this applies to objects created via C++ directly, if not, maybe could be worthy/faster just exclude this field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performance-wise, i don't know. On huge amounts of rows and sparse data, i would expect hidden class to be faster at the cost of extra memory consumption; but without benchmarking it's just a guess.
However, this difference is observable in userland, which outweights microoptimizations. I think, explicit
undefined
is better:If we get rows as objects using
SELECT * FROM ...
, we should be able to check what*
was resolved to.If we use
returnArrays: true
orstatement.setReturnArrays(true)
and keep it consistent with objects, omittingundefined
means having sparse arrays which are counterintuitive.If there is significant performance benefit from excluding fields, we can consider more explicit
useNullAsEmpty
. Or changing this from boolean touseNullAs(enum)
whilenode:sqlite
is still experimental.