Skip to content

sqlite,doc: add setReturnArrays missing docs #59074

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

geeksilva97
Copy link
Contributor

@geeksilva97 geeksilva97 commented Jul 15, 2025

The StatementSync.prototype.setReturnArrays was introduced a few months ago but its documentation was not added.

This PR adds such a documentation.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/sqlite

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. sqlite Issues and PRs related to the SQLite subsystem. labels Jul 15, 2025
Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was it backported already?

@RafaelGSS RafaelGSS added dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. labels Jul 15, 2025
@geeksilva97
Copy link
Contributor Author

Was it backported already?

I think so. When I look into the v22.x branch, I can see the code there

https://github.com/nodejs/node/blob/v22.x/src/node_sqlite.cc#L2313

@geeksilva97 geeksilva97 removed the dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. label Jul 15, 2025
@geeksilva97 geeksilva97 force-pushed the add-missing-sqlite-documentation branch from 4782318 to 0438ffb Compare July 15, 2025 14:17
### `statement.setReturnArrays(enabled)`

<!-- YAML
added: 24.0.0
Copy link
Contributor Author

@geeksilva97 geeksilva97 Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set to 24.0.0 based on #57609

@geeksilva97
Copy link
Contributor Author

We will want this to land on v22. Should I open the backport now?

@geeksilva97
Copy link
Contributor Author

Link is complaining about the hardcoded version, but I think that's expected and acceptable in this case.

@RafaelGSS
Copy link
Member

We will want this to land on v22. Should I open the backport now?

Yes, please.

@geeksilva97
Copy link
Contributor Author

We will want this to land on v22. Should I open the backport now?

Yes, please.

Okay, so I will land this, and open the backport.

@geeksilva97 geeksilva97 self-assigned this Jul 15, 2025
@geeksilva97 geeksilva97 added commit-queue Add this label to land a pull request using GitHub Actions. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. doc Issues and PRs related to the documentations. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. sqlite Issues and PRs related to the SQLite subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants