8000 bpo-44165: optimise sqlite3 statement preparation by passing string size by erlend-aasland · Pull Request #26206 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

bpo-44165: optimise sqlite3 statement preparation by passing string size #26206

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

Merged
merged 5 commits into from
Jun 2, 2021

Conversation

erlend-aasland
Copy link
Contributor
@erlend-aasland erlend-aasland commented May 18, 2021

Quoting the SQLite docs, https://sqlite.org/c3ref/prepare.html:
"If the caller knows that the supplied string is nul-terminated, then
there is a small performance advantage to passing an nByte parameter
that is the number of bytes in the input string including the
nul-terminator."

https://bugs.python.org/issue44165

@erlend-aasland
Copy link
Contributor Author

@pablogsal I recon this can pass as skip news. This is an internal micro-optimisation only. No user visible change.

@erlend-aasland erlend-aasland deleted the sqlite-prepare branch June 2, 2021 12:30
@python python deleted a comment from bedevere-bot Jun 2, 2021
@python python deleted a comment from bedevere-bot Jun 2, 2021
@erlend-aasland
Copy link
Contributor Author

This PR was broken by fffa0f9. I'll resolve the issues in a new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0