Skip to content

bpo-46249: Move set lastrowid out of the sqlite3 query loop #30489

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

Conversation

erlend-aasland
Copy link
Contributor

@erlend-aasland erlend-aasland commented Jan 8, 2022

@erlend-aasland
Copy link
Contributor Author

(GitHub would not let me resurrect GH-30371 because I deleted the original branch.)

@erlend-aasland
Copy link
Contributor Author

Skipping news as it is an internal change only. No user visible effects.

@erlend-aasland erlend-aasland changed the title bpo-46249: Move set lastrowid out of the sqlite3 query loop bpo-46249: Move set lastrowid out of the sqlite3 query loop Jan 8, 2022
@erlend-aasland erlend-aasland changed the title bpo-46249: Move set lastrowid out of the sqlite3 query loop bpo-46249: Move set lastrowid out of the sqlite3 query loop Jan 8, 2022
@felixxm
Copy link
Contributor

felixxm commented Jan 12, 2022

I confirmed this doesn't break anything in Django tests ✔️

Copy link
Member

@corona10 corona10 left a comment

Choose a reason for hiding this comment

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

I've looked closely at the change, but it doesn't seem like a regression will happen.
LGTM

@corona10 corona10 merged commit 38afeb1 into python:main Jan 22, 2022
@erlend-aasland erlend-aasland deleted the sqlite-optimise-query-loop/last-row-id branch January 22, 2022 11:23
@erlend-aasland
Copy link
Contributor Author

Thanks for reviewing, Dong-hee!

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.

5 participants