Return OK to statements without executing them #1045
Comments
renecannao
added a commit
that referenced
this issue
Jun 17, 2017
Extending mysql_query_rules with a new field: OK_msg If OK_msg is not NULL, an OK packet is sent to the client with an optional message as specified in OK_msg itself. If OK_msg is an not NULL empty string, an OK packet is sent to the client without any message. If both error_msg and OK_msg are present, error_msg is returned. This commit includes also few minor bugs, mostly related to typo that would prevent online upgrade of mysql_query_rules from early release of 1.4.0 .
|
Implemented in 1.4.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mysql_query_ruleshas already an option to filter queries returning an error iferror_msgis set.Sometime filtering queries returning an error is not the best option as the client will error if it get an error. For this reason would be better to return an OK message without executing any query to the backend.
Few examples:
set sort_buffer_size(see "set sort_buffer_size" is not properly dealt with #1044)ALTER TABLE DISABLE KEYS(cc @akuzminsky)The text was updated successfully, but these errors were encountered: