Re: [cobalt-users] MySQL & PHP

["Steven Werby" <steven-lists@xxxxxxxxxxxx>]

<mncs@xxxxxxxxxxxx> wrote:
> I have downloaded and read most of the pertinent parts of the MySQL manual
> and have a few more questions.
>
> 1. Should a new DB be created for each client asking for MySQL support?

Yes.  And some clients may need more than one DB depending on their needs.

> 2. What information will the client need to access the MySQL server?  I
> realize domain name and password but do they need any particulars on file
> locations etc...?

Domain name, username (MySQL username, not Cobalt username), password.  They'll also
need access to the MySQL client server on an external server, access to the client
server through telnet/ssh on your server, or a PHP-based, Linux-based, or
Windows-based MySQL GUI (if that meets their needs).

> It looks like I can restrict access to a particular user from a particular
> domain.  I am having some issues with the syntax to get this accomplished.
> If so can someone help me with the statements for creating the DB giving
> their user id only the permissions necessary for them to work on it?  I do
> not want them to be able to mess up anything other than their own stuff.

Consult the MySQL manual at mysql.com or one of the mirror sites concerning "grant
tables".  I also posted a URL for a grant tables tutorial within the last couple of
weeks so check this list's archives.  You can either use the "grant" command or
insert/update commands followed by "flush privileges" from the mysql prompt to modify
the tables within the mysql database (where the grant table system resides).

> I am learning this stuff at breakneck speed but I do not want to make a
> costly mistake by screwing up.

Make sure you read up on "mysqldump" so you can backup the data files properly (and
restore them if necessary) and myisamchk or isamck to check and repair tables.  You
*do not* want to wait until your hard drive dies, you or a client deletes or corrupts
a database, or something else catostrophic happens to learn how to use these tools.
Also take a look at the general logging and update logging options which are good for
debugging and also for rebuilding critical tables to the point of a catostrophic
event.  And grab MySQL by Paul DuBois from bookpool.com (where I bought it, cheapest
on the net at the time, showed up in 2 days).

Steven Werby {steven-lists@xxxxxxxxxxxx}