[client] var not working
Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. Thanks, Lou Olsten
Re: [client] var not working
hi Lou, I believe this is a recent feature so make sure you on on 4.0.18 if possible, I know is was added before 4.0.14. I am not sure this works on 3.23. Ken - Original Message - From: Lou Olsten [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 29, 2004 10:38 AM Subject: [client] var not working Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. Thanks, Lou Olsten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: [client] var not working
Place the SET FOREIGN_KEY_CHECKS=0 in the beginning of the file that contains the backup or run this command from the command line before you import the file. -Original Message- From: Lou Olsten To: [EMAIL PROTECTED] Sent: 4/29/04 9:38 AM Subject: [client] var not working Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. Thanks, Lou Olsten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: [client] var not working
Lou Olsten [EMAIL PROTECTED] wrote: Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. You should add the following statement to the beginning of the dump file: SET FOREIGN_KEY_CHECKS = 0; or load dump file like: mysql SET FOREIGN_KEY_CHECKS = 0; mysql SOURCE dump_file.sql; mysql SET FOREIGN_KEY_CHECKS = 1; -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: [client] var not working
At 10:38 -0400 4/29/04, Lou Olsten wrote: Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. There is an example that shows how to use the variable on this page: http://dev.mysql.com/doc/mysql/en/InnoDB_foreign_key_constraints.html I got to this page by going to: http://dev.mysql.com/doc/mysql/en/index.html Then I typed foreign_key_checks into the search box and clicked the Go button. The first page in the list of hits is the one shown above. -- 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]
Re: [client] var not working
Thanks, Paul. You appear frustrated that I didn't look in the docs first. 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. 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. 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. Thanks, Lou - Original Message - From: Paul DuBois [EMAIL PROTECTED] To: Lou Olsten [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, April 29, 2004 11:21 AM Subject: Re: [client] var not working At 10:38 -0400 4/29/04, Lou Olsten wrote: Per a response from Victoria (thanks, BTW!) I see that I can reload my InnoDB RI's data by turning off SET FOREIGN_KEY_CHECKS = 0 during the restore. I then tried to go to the machine where the dumps were going to be restored and set this variable in the [client] section of my.cnf. But when I try to connect after that, I get an: ERROR: unknown variable 'foreign_key_checks=0'. I then tried using: set variable=foreign_key_checks=0 ...but got the same result. Is there a list of variables that I *can* use in the [client] section, or am I just doing something wrong. There is an example that shows how to use the variable on this page: http://dev.mysql.com/doc/mysql/en/InnoDB_foreign_key_constraints.html I got to this page by going to: http://dev.mysql.com/doc/mysql/en/index.html Then I typed foreign_key_checks into the search box and clicked the Go button. The first page in the list of hits is the one shown above. -- 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]
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. 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]
Re: [client] var not working
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]
