mark wrote (1/9/2004):
On Friday 09 January 2004 01:44 pm, Diana Soares wrote:
From the manual, check:
* the file must be on the server * you must specify the full pathname to the file (ok, you did this) * you must have the FILE privilege
Ahhh! Misunderstood that one. Got it, now. Thanks.
Still don't understand why grant doesn't work with 3.23, and why I have to do an update to the user table to give the correct permissions. The docs *seem* to say that grant works, as of 3.22
mark
GRANT does work in 3.23. Is that in reference to your earlier question from 1/6?
mark wrote (1/6/2004):
Just fired up mysql 3.23.53 *
Created a d/b, and then created an admin user for that d/b, using GRANT ALL ON URCMS.* TO urcms_admin IDENTIFIED BY 'changeme' WITH GRANT OPTION;
Ok, it never prompts me for a password, nor did it let me, as that user, use URCMS. I looked in mysql.db, and the host for that user was %, which according to the reference, *should* let me do that from any host.
If it didn't prompt you for a password, you forgot to put -p on the command line. You need to connect with
mysql -u urcms_admin -p
Without -p, it expects that either you don't have a password, or the one set in your my.cnf will work. If it lets you in without a password, then you aren't connected as this user. Try
SELECT CURRENT_USER()
to see who mysql thinks you are.
At any rate, it only let me go to the d/b after, as root, I did GRANT ALL ON URCMS.* TO [EMAIL PROTECTED] WITH GRANT OPTION;
I would assume that % should include localhost. Am I missing something here?
Probably. % will match localhost, unless something more specific matches localhost. Before you created [EMAIL PROTECTED], you were most likely connecting as the anonymous (''@localhost) user, as Ari Davidow earlier suggested. Because host takes precedence over user, ''@localhost, rather than [EMAIL PROTECTED], is the match for [EMAIL PROTECTED]
There are 2 solutions:
1) Most people (I think) delete the anonymous user, as Ari suggested. Once ''@localhost is gone, [EMAIL PROTECTED] will match.
2) Explicitly create a [EMAIL PROTECTED] mysql, as Michael Wittmann suggested and you did. This works because [EMAIL PROTECTED] is more specific than ''@localhost, which, in turn, is still more specific than [EMAIL PROTECTED]
See <http://www.mysql.com/doc/en/Connection_access.html> for more.
mark
* Please don't tell me to upgrade to 4.x. I'm working on some software, and I do *not* want it to require Only The Latest Version. Since many distros are still shipping with 3.23, I want it to be compatable with what they're running, and not force them to upgrade, *unless* this is a known bug. In that case, I have no problem upgrading to the next patch level.
3.23 should be fine.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
