At 12:22 -0400 4/29/04, Lou Olsten wrote:
Thanks, Paul. You appear frustrated that I didn't look in the docs first.

Um, no.


I gave instructions for finding the answer to a question that you were
asking.  I don't think that translates into any frustration about your
use of the manual.  I didn't know if you looked there or not.

I had been to that page (and thoroughly read it) after Victoria's reply.
Prior to the reply, I tried searching but wasn't sure what to search for, so
didn't find what I was looking for.  The real gist of my question was:

<<Is there a list of variables that I *can* use in the [client] section, or
am I just doing something wrong.>>

The only options that can go in the [client] section are those options that are understood by *all* client programs that read option files. Or at least all client programs that you happen to use that read option files. So if myprog1 --help lists an option and myprog2 --help doesn't list an option, you shouldn't put it in [client].


I'm trying to figure out why I couldn't just put it in the [client] section because I'm trying to understand the entire product on a deeper level. I've thoroughly read http://dev.mysql.com/doc/mysql/en/Option_files.html and it appears that this request (knowing all the config file options) has been made by others, so I felt no need to post it there in addition to the others.

Run the program with the --help option to find out what options you can list in an option file. If an option is specific to a given program, put it in the option file section named for that specific program. E.g., an option that mysqldump supports but other programs do not should go in the [mysqldump] section.

I've noticed those comments in the online manual as well.  Personally,
I don't really see the point of trying to list every single possible
option on that page.  The information for particular programs is given
in the sections that describe those programs, and makes more sense in
that context.


So back to my question... is looking at the command line options for a
program a good way to figure out what can go into the option file or does
that not always hold true?  SHOW VARIABLES?  I noticed that SET
FOREIGN_KEY_CHECKS doesn't appear in the SHOW VARIABLES list.  The only
place I found it was by querying @@session.FOREIGN_KEY_CHECKS.

Well, one point here is that FOREIGN_KEY_CHECKS isn't a client option. But the fact that it doesn't show up in SHOW VARIABLES is, I agree, a problem. There is some talk going on behind the scenes about this, but it isn't solved yet. This variable and other such are listed here:

http://dev.mysql.com/doc/mysql/en/SET_OPTION.html


-- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to