* Hamlin Nicholas-qa568 > I have added some extra fields to the mysql.user table, namely: > full_name VARCHAR(255) > job VARCHAR(255) > location VARCHAR(255) > phone VARCHAR(255) > reminder VARCHAR(255) NOT NULL > ip_addr VARCHAR(255) NOT NULL > > I want to store these values for each person that creates a new > account on my database.
Yes, one might think that is a good idea, but it isn't... :) The "mysql" database is an internal system database, you are probably better of considering it read only... The GRANT and REVOKE commands modify these tables. <cut> > > Any ideas would be appreciated so that I can make sure that some > unsuspecting user doesn't throw some value in their entry that > will cause the system not to work for them. Or maybe there's a > better way of going about this? Create your own user tables in your own database, and use only one or a few real mysql users... maybe one for read only, one for doing changes and one for admin, depending on your application, of course. This means you must have username and password columns in your table in addition to those you had planned, and you check the login against this. If it is ok, you do the real login to mysql with the uname/pw you wish for this user. -- Roger --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
