mariadb/client
Monty c4ebb2bd04 Fixed that mysql_upgrade doesn't give errors about mariadb.sys
The reason for this fix was that when I tried to run mysql_upgrade
at home to update an old 10.5 installation, mysql_upgrade failed
with warnings about mariadb.sys user not existing.

If the server was started with --skip-grants, there would be no warnings
from mysql_upgrade, but in some cases running mysql_upgrade again could
produce new warnings.

The reason for the warnings was that any access of the mysql.user view
will produce a warning if the mariadb.sys user does not exists.

Fixed with the following changes:
- Disable warnings about mariadb.sys user not existing
- Don't overwrite old mariadb.sys entries in tables_priv and global_priv
- Ensure that tables_priv has an entry for mariadb.sys if the user exists.
  This fixes an issue that tables_priv would not be updated if there
  was a failure directly after global_priv was updated.
2022-04-04 16:14:22 +03:00
..
async_example.c
client_priv.h
CMakeLists.txt
completion_hash.cc
completion_hash.h
echo.c
my_readline.h
mysql.cc
mysql_plugin.c
mysql_upgrade.c
mysqladmin.cc
mysqlbinlog.cc
mysqlcheck.c
mysqldump.c
mysqlimport.c
mysqlshow.c
mysqlslap.c
mysqltest.cc
readline.cc
sql_string.cc.dontuse
sql_string.h.dontuse