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
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:
'\'\' \'\''
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
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.
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
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
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
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
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
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,
10 matches
Mail list logo
