Request Verification

• For each request issued via a connection, the server determines whether the user has sufficient privileges for the request.
  • This is where the privilege columns in the grant tables come into play.
  • These privileges can come from any of the user, db, host, tables_priv, columns_priv, or procs_priv tables.

• The user table grants privileges that are assigned the user on a global basis and that apply no matter what the default database is.
  • Grant privileges in the user table only to superusers such as database administrators.
  • For other users, leave all privileges in the user table set to 'N' and grant privileges at more specific levels only.

• The db and host tables grant database-specific privileges.
  • Values in the scope columns of these tables can take the following forms:
    • The wildcard characters ‘%’ and ‘_’ can be used in the Host and Db columns of either table.
      • These have the same meaning as for pattern-matching operations performed with the LIKE operator.
  • A ‘%’ Host value in the db table means "any host".
  • A blank Host value in the db table means "consult the host table for further information".
  • A ‘%’ or blank Host value in the host table means "any host".
  • A ‘%’ or blank Db value in either table means "any database".
  • A blank User value in either table matches the anonymous user.

How does the server sort the db table and the host table?

---

---

© 2007 John Michael Pierobon

Notes