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 this problem for just the same reason)
http://dev.mysql.com/doc/mysql/en/Reserved_words.html However, mysqldump does have the option to backtick-quote all field names in its CREATE TABLE statements. The full list of options is available if you run mysqldump --help and the option you are interested in can be turned on either with -Q or --quote-names. That makes your dump command read daemon0% mysqldump -Q -S mysqld-daemon0.sock --master-data --all-databases > daemin0-dump.sql Shawn Green Database Administrator Unimin Corporation - Spruce Pine Daniel Kasak <[EMAIL PROTECTED]> wrote on 11/09/2004 06:16:38 PM: > 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 with mysqldump ? > > -RG > > '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 it solves. See above example. > > -- > Daniel Kasak > IT Developer > NUS Consulting Group > Level 5, 77 Pacific Highway > North Sydney, NSW, Australia 2060 > T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > email: [EMAIL PROTECTED] > website: http://www.nusconsulting.com.au > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
