Difference of MySQL 8.0 syntax from MariaDB

1. MySQL 8.0 supports a different compression algorithm for each table (table option COMPRESSION). MariaDB supports defining one global algorithm for all tables. Perhaps, while MariaDB does not have the ability to set different algorithms, it is possible to make, like syntactic sugar, the possibility of using the COMPRESSION table option if the algorithm specified in it matches the global one, otherwise give an error or warning.
2. In MariaDB, the CREATE DATABASE does not have the encryption option, but the encryption option is available for individual tables. It might make sense to add this option, as in MYSQL 8.0.
3. MariaDB lacks the

construct for compatibility with ODBC. This helps with compatibility with some third-party applications, but is not official ODBC syntax.
4. MySQL 8.0 supports options for Password Reuse Policies, Password-requiring Policies, Double Password Support (https://dev.mysql.com/doc/mysql-security-excerpt/8.0/en/password-management.html#password-reuse-policy). Some time ago, a movement was being considered towards supporting these options (https://jira.mariadb.org/plugins/servlet/mobile#issue/MDEV-9245).
5. You were opposed to supporting the ALL keyword in SET ROLE, as this is not in the standard (see comments
https://mariadb.com/kb/en/set-default-role/#comment_2830). Is it right now?
 6. In MySQL 8.0, when creating a user, you can specify a comment and attributes. This is a regular JSON column in the user table, maybe it makes sense to add support for this in MariaDB