Skip to content

sqlite: Fix #616 #627

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 1 commit into from
Oct 13, 2020
Merged

sqlite: Fix #616 #627

merged 1 commit into from
Oct 13, 2020

Conversation

Patryk27
Copy link
Contributor

Explanation and benchmark has been already provided inside #616, so - without further ado - here's the code.

@fosskers
Copy link

fosskers commented Aug 15, 2020

I see good effects with this fix in my own code.

@Patryk27
Copy link
Contributor Author

Patryk27 commented Sep 2, 2020

Ping, ping @mehcode? :-)

@complexspaces
Copy link

@abonander @mehcode If you have any time, could this one be looked at? Its been open for nearly 2 months and others have seen it fix things. A project I'm working on is also experiencing high CPU usage from the bug on a number of platforms.

@mehcode mehcode merged commit ca07158 into launchbadge:master Oct 13, 2020
@mehcode
Copy link
Member

mehcode commented Oct 13, 2020

I really appreciate the fix. Thank you for the confirmations. That helps.

@Patryk27 Patryk27 deleted the fix/616-statement-worker branch October 13, 2020 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants