-
-
Notifications
You must be signed in to change notification settings - Fork 104
[18.0][FIX] mail_message_search : prevent db crash #125
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
Conversation
Co-authored-by: Florent de Labarre <florent.mirieu@gmail.com>
|
Hi @yostashiro, @AungKoKoLin1997, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional review
flotho
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi
Thanks for the PR.
I get the point.
Yet I'm wondering why you didn't defined a default value as a system parameter.
For sure one can argue that "BIG" database depends on so many factor as the server size, setup, etc... yet if you're pointing 5000 in you exemple maybe you've experienced such kind of limitation.
hat is you PoV on this?
Regards
@flotho |
flotho
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
yostashiro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be good to have a default value as @flotho suggests, but I'm not against having no value either.
|
This PR has the |
etobella
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense
|
/ocabot merge patch |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
Congratulations, your PR was merged at 718c636. Thanks a lot for contributing to OCA. ❤️ |
Supersedes #72
@qrtl QT5088