Re: mysqldump output

2009-07-23 Thread peng yao
#mysqldump -u username -p -h mysqld_host databasename database_name.sql username is the mysqld server login name mysqld_host is the mysqld server address or hostname databasename is the database which you should dump You can use man mysqldump or mysqldump --help to get more infomation 2009/7/21

Re: mysqldump output

2009-07-20 Thread zhu dingze
we need more information, such as your client and server version, the command that exactly your input etc. 2009/7/14 JingTian jingtian.seu...@gmail.com hi all, i use mysqldump to backup my database, the command line is; mysqldump -p -u -h database_name database_name.sql i find in the

mysqldump output

2009-07-14 Thread JingTian
hi all, i use mysqldump to backup my database, the command line is; mysqldump -p -u -h database_name database_name.sql i find in the database_name.sql, there is a line: Not dumping tablespaces as no INFORMATION_SCHEMA.FILES table on this server can anyone tell me what does it mean? thanks

Error importing from mysqldump output

2005-06-28 Thread Daniel Kasak
Hi all. I'm testing out mysql-5.0.7. I dumped a database from 5.0.4 with the command: mysqldump --opt DB_NAME DB_NAME.sql -p Now I'm importing with: mysql DB_NAME DB_NAME.sql -p The data has a field which has some quotes in it. The field looks like this ( all quotes included ): '' '' ie 2x

Re: Error importing from mysqldump output

2005-06-28 Thread Daniel Kasak
Daniel Kasak wrote: The data has a field which has some quotes in it. The field looks like this ( all quotes included ): '' '' ie 2x single quotes, a space, and 2x single quotes. Don't ask me why. I didn't put it there. Anyway, mysqldump has packaged this field as follows: '\'\' \'\''

Re: Error importing from mysqldump output

2005-06-28 Thread Michael Stassen
Daniel Kasak wrote: Hi all. I'm testing out mysql-5.0.7. I dumped a database from 5.0.4 with the command: mysqldump --opt DB_NAME DB_NAME.sql -p Now I'm importing with: mysql DB_NAME DB_NAME.sql -p The data has a field which has some quotes in it. The field looks like this ( all quotes

Re: Error importing from mysqldump output

2005-06-28 Thread Daniel Kasak
Michael Stassen wrote: Mysql reports the first thing it didn't understand, which isn't necessarily the first thing wrong. I note that it thought \' was a command, which implies it didn't see the preceding ' as the *start* of a string, which implies something went wrong earlier in the line.

Re: error importing from mysqldump output

2004-11-10 Thread SGreen
I agree that using a reserved word for any purpose than that for which it is reserved is a poor design choice. I also strongly encourage you to change the name of that field and any others that conflict with the reserved words list (the field name desc is another name that frequently causes

error importing from mysqldump output

2004-11-09 Thread Russell E Glaue
I did a mysqldump from serverA, took that output and did the following as illustrated below to import into serverB. why did I get an error? Did mysqldump output the wrong SQL syntax? I would not think so, but I got this error which says so. I am using mysql-4.0.20 on both servers. I am

Re: error importing from mysqldump output

2004-11-09 Thread Daniel Kasak
Russell E Glaue wrote: snipped ERROR 1064 at line 14071: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'order int(1) NOT NULL default '0', PRIMARY KEY (moduleID), snipped Would this possibly be a bug

Re: error importing from mysqldump output

2004-11-09 Thread Russell E Glaue
Daniel Kasak wrote: Russell E Glaue wrote: snipped ERROR 1064 at line 14071: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'order int(1) NOT NULL default '0', PRIMARY KEY (moduleID), snipped Would this

Re: error importing from mysqldump output

2004-11-09 Thread Daniel Kasak
Russell E Glaue wrote: 'order' is a reserved word. I would rename that field, pronto! In my opinion the bug is not in mysqldump, but in mysql allowing you to use a fieldname that is a reserved word. And yes I know about the backticks that mysqlcc uses, but surely this causes more problems than

Re: error importing from mysqldump output

2004-11-09 Thread Paul DuBois
At 10:33 +1100 11/10/04, Daniel Kasak wrote: Russell E Glaue wrote: 'order' is a reserved word. I would rename that field, pronto! In my opinion the bug is not in mysqldump, but in mysql allowing you to use a fieldname that is a reserved word. And yes I know about the backticks that mysqlcc uses,

how to change mysqldump output txt file format?

2004-09-24 Thread Monet
Hello everyone, In mysqldump output txt file, all datetime, varchar, text fields value are surrounding by single quotes. Is there any way that the single quotes can be replaced by double quotes in the txt file? Furthermore, if you have a single quote in text field, it will automatically replaced

Re: how to change mysqldump output txt file format?

2004-09-24 Thread Jim Grill
Hello everyone, In mysqldump output txt file, all datetime, varchar, text fields value are surrounding by single quotes. Is there any way that the single quotes can be replaced by double quotes in the txt file? Furthermore, if you have a single quote in text field, it will automatically

Re: how to change mysqldump output txt file format?

2004-09-24 Thread SGreen
:40 PM: Hello everyone, In mysqldump output txt file, all datetime, varchar, text fields value are surrounding by single quotes. Is there any way that the single quotes can be replaced by double quotes in the txt file? Furthermore, if you have a single quote in text field

Re: how to change mysqldump output txt file format?

2004-09-24 Thread Jim Grill
Subject: Re: how to change mysqldump output txt file format? Jim - He needs to change the format because he isn't exporting from one MySQL database to another His destination database doesn't like the escaped single quotes. Here is the manual page for mysqldump: http

Re: how to change mysqldump output txt file format?

2004-09-24 Thread Monet
Pine Jim Grill [EMAIL PROTECTED] wrote on 09/24/2004 02:35:40 PM: Hello everyone, In mysqldump output txt file, all datetime, varchar, text fields value are surrounding by single quotes. Is there any way that the single quotes can be replaced by double quotes in the txt

Re: how to change mysqldump output txt file format?

2004-09-24 Thread Jim Grill
Yeah. I am moving data from mysql server to sql server. Because I have single quote in some strings, it generated errors when I ran mysqldump scripts in sql server to import data in. i.e. strings Here's, Martin's ,... caused trouble. Does that mean sql didn't recognize escaped single

Re: how to change mysqldump output txt file format?

2004-09-24 Thread Monet
Thanks Jim. Great suggestions. I will try both to see which one is better for my case. Appreciated your help. Monet --- Jim Grill [EMAIL PROTECTED] wrote: Yeah. I am moving data from mysql server to sql server. Because I have single quote in some strings, it generated errors when I ran

Restoring db from mysqldump output problem...

2002-12-20 Thread Jeff Snoxell
Hello, I've successfully backed up my database to JeffsDB.sql using mysqldump with the -opt option. When I try to restore it using: mysql -h myhost -u myusername -ppassword JeffsDB JeffsDB.sql I get: ERROR 1065 at line 21: Query was empty Now, line 21 of the SQL file contains: /*!4

Re: gunk in mysqldump output

2002-04-16 Thread Bill Marrs
I don't have --no-disable-keys in my version of myqldump (Ver 8.21 Distrib 3.23.48). (-K doesn't seem to do anything, I assume it's the default). I actually wouldn't mind disabling keys for the load, but I don't understand how the /*!4 ... stuff is suppose to get used. Is this a

gunk in mysqldump output

2002-04-15 Thread Bill Marrs
In some recent release of MySQL, lines like this: /*!4 ALTER TABLE States DISABLE KEYS */; ...were added to the output of mysqldump --opt. This causes my usually load statement: mysql dumpfile ...to fail with ERROR 1046 at line 11: No Database Selected. If I do mydsql -f dumpfile it

Re: gunk in mysqldump output

2002-04-15 Thread Nick Pasich
Use option -K or --no-disable-keys with myqldump. Date: Mon, 15 Apr 2002 09:37:43 -0400 To: [EMAIL PROTECTED] From: Bill Marrs [EMAIL PROTECTED] Subject: gunk in mysqldump output In some recent release of MySQL, lines like this: /*!4 ALTER TABLE States DISABLE KEYS

mysqldump output file not valid as input file for mysql client

2001-02-22 Thread loschert
ganization: Matt Loschert | email: [EMAIL PROTECTED]| Software Engineer | web: http://www.servint.net/ | ServInt Internet Services | phone: (703) 847-1381 | MySQL support: none Synopsis: mysqldump output file

Re: mysqldump output file not valid as input file for mysql client

2001-02-22 Thread Sinisa Milivojevic
hone: (703) 847-1381 | MySQL support: none Synopsis: mysqldump output file not valid as input file for mysql client Severity: non-critical Priority: medium Category: mysql Class: sw-bug Release:mysql-3.23.33 (Source distribution) E

Re: mysqldump output file not valid as input file for mysql client

2001-02-22 Thread Matt Loschert
eb: http://www.servint.net/ | ServInt Internet Services| phone: (703) 847-1381 | MySQL support: none Synopsis: mysqldump output file not valid as input file for mysql client Severity: non-critical Priority: medium Category: mysql Class:

Re: mysqldump output file not valid as input file for mysql client

2001-02-22 Thread Sinisa Milivojevic
QL support: none Synopsis: mysqldump output file not valid as input file for mysql client Severity: non-critical Priority: medium Category: mysql Class: sw-bug Release: mysql-3.23.33 (Source distribution) Environment:

Re: mysqldump output file not valid as input file for mysql client

2001-02-22 Thread Matt Loschert
t Internet Services | phone: (703) 847-1381 | MySQL support: none Synopsis: mysqldump output file not valid as input file for mysql client Severity:non-critical Priority:medium Category:mysql Class: sw-bug

mysql hanging on mysqldump output

2001-02-07 Thread Lance Lovette
I am trying to copy data from one database to another using output from mysqldump version 8.11 distributed with 3.23.28-gamma. The problem is that part way through importing the data into the target database, mysql just hangs. When I show the process list, there is only one query, and it's stuck