This grants root access with the same password from any machine in *.example.com: GRANT ALL PRIVILEGES ON *.* TO ‘root’@’%.example.com’ IDENTIFIED BY ‘some_characters’ WITH GRANT OPTION; FLUSH PRIVILEGES; If name resolution is not going to work, you may also grant access by IP or subnet: GRANT ALL PRIVILEGES ON *.* TO ‘root’@’192.168.1.%’ IDENTIFIED … Read more
GRANTs on different objects are separate. GRANTing on a database doesn’t GRANT rights to the schema within. Similiarly, GRANTing on a schema doesn’t grant rights on the tables within. If you have rights to SELECT from a table, but not the right to see it in the schema that contains it then you can’t access … Read more
All commands must be executed while connected to the right database cluster. Make sure of it. Roles are objects of the database cluster. All databases of the same cluster share the set of defined roles. Privileges are granted / revoked per database / schema / table etc. A role needs access to the database, obviously. … Read more
TO ‘user’@’%’ % is a wildcard – you can also do ‘%.domain.example’ or ‘%.123.123.123’ and things like that if you need.
GRANT on the database is not what you need. Grant on the tables directly. Granting privileges on the database mostly is used to grant or revoke connect privileges. This allows you to specify who may do stuff in the database if they have sufficient other permissions. You want instead: GRANT ALL PRIVILEGES ON TABLE side_adzone … Read more