You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the mysql commit, we can see that is_errors is deleted directly almost. But check the code, like the
the items related function, push_warning|my_error is used to mark errors. So use is_error is a better solution.
Describe the solution you'd like
adapt the code of mysql8.0 Describe alternatives you've considered
just delete the function. Additional context
The text was updated successfully, but these errors were encountered:
lujiashun
changed the title
feature(StoneDB 8.0): fix: thd->no_errors no_errors is deleted
feature(StoneDB 8.0): thd->no_errors no_errors is deleted
Sep 26, 2022
lujiashun
pushed a commit
to lujiashun/stonedb
that referenced
this issue
Sep 26, 2022
[summary]
1 no_erros is used little in mysql5.7,eg in Item::update_null_value and so on.
2 code is refacted in 8.0,and use push_warning or my_error function to mark errors in is_error function.
[summary]
1 no_erros is used little in mysql5.7,eg in Item::update_null_value and so on.
2 code is refacted in 8.0,and use push_warning or my_error function to mark errors in is_error function.
[summary]
1 no_erros is used little in mysql5.7,eg in Item::update_null_value and so on.
2 code is refacted in 8.0,and use push_warning or my_error function to mark errors in is_error function.
Is your feature request related to a problem? Please describe.
mysql/mysql-server@9fce6b0
in the mysql commit, we can see that is_errors is deleted directly almost. But check the code, like the
the items related function, push_warning|my_error is used to mark errors. So use is_error is a better solution.
Describe the solution you'd like
adapt the code of mysql8.0
Describe alternatives you've considered
just delete the function.
Additional context
The text was updated successfully, but these errors were encountered: