Peter Schoenster wrote:
Hi,
I installed an app which used
option
as a field. It worked fine in version 3.23 on my play box. I then moved
the app to another box (4.0.15) and when I tried to dump it in (mysql -u
x -px database <dump_from_other_box) it balked at the use of option.
I suspected reserved word and such was confirmed on the mysql site.
So I moved the database directory from play box to live box. That worked. All was well. But I worry.
Then, I went to the mysql site and read some more and saw a reason for those annoying backticks in phpmyadmin. I see that I could have done the original dump had I put option in backticks.
So now I'm a bit confused why I should avoid reserved words (other than to avoid backticks which is enough for me but I'm curious).
MySQL stores field names without backticks in FRM file, so it doesn't matter if the field "otpion" was created under 3.23 using word "option" without backticks, or under 4.0 using "option" with backticks.
Will awful things happen to me in the future?
As you're going to use "option" in backticks, no, awful things should not happen.
Peter
-- For technical support contracts, visit https://order.mysql.com/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Alexander Barkov <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer /_/ /_/\_, /___/\___\_\___/ Izhevsk, Russia <___/ www.mysql.com +7-912-856-80-21
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
