Paul, please see below... ----- Original Message ----- From: "Paul DuBois" <[EMAIL PROTECTED]> To: "Lou Olsten" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, April 29, 2004 1:00 PM Subject: Re: [client] var not working
> 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. Long day. Sorry for the intimation. ;-) > 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]. Great. Thanks. > 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. Got it. Thanks. > > 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. Agreed. And especially being that I can use the --help option as stated above. That way it stays consistent across versions, etc. > 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. Fair enough! > This variable and other such are listed here: > > http://dev.mysql.com/doc/mysql/en/SET_OPTION.html > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
