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
[ModLog] Optimise get_next_case_number() #2908
[ModLog] Optimise get_next_case_number() #2908
Conversation
Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
one last change from me after some consideration.
Let's go ahead and make get_next_case_number
private and remove it from __all__
There's not a reason to expose this function outside of modlog, and the next release is one which allows for removing this from the public API.
Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
@mikeshardmind I've actually gone ahead and removed the function all together. It was only used in one place, and that place is kind of easier to understand (w.r.t. lock usage) if it just uses config directly. |
Apparently it *isn't the only place (discussion: discord)
Signed-off-by: Toby Harradine <tobyharradine@gmail.com>
We've noticed that this is taking an obscenely long time on very large servers.