SpirirHost Support Centre: MySQL Reference Manual p.206

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

206 MySQL Technical Reference for Version 4.0.3 matches both the connecting hostname and user name. (The '%'/'jeffrey' entry would have matched, too, but it is not the rst match in the table.) Here is another example. Suppose the user table looks like this: +----------------+----------+- | Host | User | ... +----------------+----------+- | % | jeffrey | ... | thomas.loc.gov | | ... +----------------+----------+- The sorted table looks like this: +----------------+----------+- | Host | User | ... +----------------+----------+- | thomas.loc.gov | | ... | % | jeffrey | ... +----------------+----------+- A connection from thomas.loc.gov by jeffrey is matched by the rst entry, whereas a connection from whitehouse.gov by jeffrey is matched by the second. A common misconception is to think that for a given user name, all entries that explicitly name that user will be used rst when the server attempts to nd a match for the connection. This is simply not true. The previous example illustrates this, where a connection from thomas.loc.gov by jeffrey is rst matched not by the entry containing 'jeffrey' as the User eld value, but by the entry with no user name! If you have problems connecting to the server, print out the user table and sort it by hand to see where the rst match is being made. 4.2.10 Access Control, Stage 2: Request Verication Once you establish a connection, the server enters Stage 2. For each request that comes in on the connection, the server checks whether you have sucient privileges to perform it, based on the type of operation you wish to perform. This is where the privilege elds in the grant tables come into play. These privileges can come from any of the user, db, host, tables_priv, or columns_priv tables. The grant tables are manipulated with GRANT and REVOKE commands. See Section 4.3.1 [GRANT], page 212. (You may nd it helpful to refer to Section 4.2.6 [Privileges], page 197, which lists the elds present in each of the grant tables.) The user table grants privileges that are assigned to you on a global basis and that apply no matter what the current database is. For example, if the user table grants you the DELETE privilege, you can delete rows from any database on the server host! In other words, user table privileges are superuser privileges. It is wise to grant privileges in the user table only to superusers such as server or database administrators. For other users, you should leave the privileges in the user table set to 'N' and grant privileges on a database-specic basis only, using the db and host tables. The db and host tables grant database-specic privileges. Values in the scope elds may be specied as follows:

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide