Incoming from Paul DuBois: > > At 16:39 -0600 10/2/05, s. keeling wrote: > > > >The admin account, with no password, doesn't function at all. perl > >programs appear to ignore ~/.my.cnf forcing me to open() them and > >slurp username and password that way. > > > >How is this supposed to work? Surely, you're not all embedding > >passwords in your source, are you? How can I have separate user and > >admin accounts working via ~/.my.cnf from the same login account? > > I think I'd probably set up aliases that invoke mysql or mysqladmin > with a --defaults-extra-file option that contains the username/password > for the appropriate account.
Groan. More stuff to learn, configure, maintain, and memorize. I'm trying to replicate Unix's "root vs. mere user" security paradigm in MySQL. I can do "drop table" as sbk without hurting myself. Doing it as keeling risks data loss. How about if I submit a feature request? Parse the command line. If command == bar and MySQL user == foo, find foo's password stanza for bar in ~/.my.cnf, and use that password. That shouldn't be difficult. Why does a perl program run by my login username ignore MySQL's ~/.my.cnf? Are MySQL users really embedding passwords in their code? How do I use the passwordless admin account? Should that stanza just be deleted from .my.cnf? How do other db's handle this, or do they? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
