

Statement delimiters cannot be used within executable comments. *M!50701 MariaDB-10.x does not ignore this */ Note: comments which have a version number in the range 50700.99999 that use MariaDB-style executable comment syntax are still executed.

This is needed to skip features introduced in MySQL-5.7 that are not ported to MariaDB 10.x yet. Starting from MariaDB 10.0.7, MariaDB ignores MySQL-style executable comments that have a version number in the range 50700.99999.
#Comment mariadb Patch
The first number is the major version, the second 2 numbers are the minor version and the last 2 is the patch level.įor example, if you want to embed some code that should only execute on MySQL or MariaDB starting from 5.1.0, you would do the following: /*!50100 MySQL and MariaDB 5.1.0 (and above) code goes here. The numbers, represented by ' #' in the syntax examples above specify the specific the minimum versions of MySQL and MariaDB that should execute the comment. MySQL and MariaDB executable comment syntax: /*! MySQL or MariaDB-specific code */Ĭode that should be executed only starting from a specific MySQL or MariaDB version: /*!# MySQL or MariaDB-specific code */ This way, if you have SQL code that works on MySQL and MariaDB, but not other databases, you can wrap it in a MySQL executable comment, and if you have code that specifically takes advantage of features only available in MariaDB you can use the MariaDB specific format to hide the code from MySQL. MariaDB supports both MySQL's executable comment format, and a slightly modified version specific to MariaDB. These special comments allow you to embed SQL code which will not execute when run on other databases, but will execute when run on MariaDB. Executable CommentsĪs an aid to portability between different databases, MariaDB supports executable comments. Nested comments are possible in some situations, but they are not supported or recommended. Comments of this form can span multiple lines: SELECT * FROM users /* This is a C style comments from an opening ' /*' to a closing ' */'.The space after the two dashes is required (as in MySQL). From a ' #' to the end of a line: SELECT * FROM users # This is a comment.Put back the copy of /usr/lib64/libmysqlclient.so.18 you made at the start and you can restart postfix.There are three supported comment styles in MariaDB: Rpm -e -nodeps "mariadb-5.5.86_64"ĭelete left over files and folders (which also removes any databases): rm -f /var/log/mariadb ago I think MariaDB really gave me a better performance but I also had some problems with it. ago For me I'm switched to MariaDB after adding energy monitoring (18 values almost every second) The increase in speed for history was tremendous. Rpm -e -nodeps "mariadb-server-5.5.86_64" 36 comments Best Add a Comment -lll- 4 mo. Then remove the mariadb packages using (changing to your versions): rpm -e -nodeps "mariadb-libs-5.5.86_64" To get around this and keep postfix in place, first make a copy of /usr/lib64/libmysqlclient.so.18 (which is what postfix depends on) and then use: rpm -qa | grep mariadb

Removing using yum will also remove postfix and perl-DBD-MySQL. Later versions of CentOS 7 have MariaDB included as the base along with PostFix which relies on MariaDB.
#Comment mariadb update
To update and answer the question without breaking mail servers.
