[ciapug] Mysql upgrade

[David Champion]

SELECT `select` FROM `from` WHERE `where` = "???"

:p

-dc

Tim Champion wrote:
> I wouldn't personally consider putting backticks around field names to
> be a hack at all. Any time I have a field name that I think could
> possibly be a MySQL reserved work, i put backticks around it just for
> good measure. We have several field names in a largish db that are
> MySQL reserved words ... not a big deal really.
> 
> On 7/11/06, Dave J. Hala Jr. <dave at 58ghz.net> wrote:
> 
>> I'm proud to say that the upgrade on my webserver's database server went
>> well. I went from Rh 9 and mysql 3.26x to Centos 4 and mysql 4.1 Only a
>> couple of surprises, and they were fairly trivial.
>>
>> I found that I had a field  in a mysql 3.26 table that was illegal in
>> 4.1. This issue was resolved by placing  backtics around it in the sql
>> statements that use it.
>>
>> Kinda of a hack actually. Looks like next version of  the code, I'll
>> have to change that field name.
>>
>> Passwords are encrypted with a longer key in 4.1, this caused a problem
>> with the client on the webserver. At this time it was important to not
>> make any major changes to the webserver, so I told mysql 4.1 to use
>> "old-passwords" in the my.cnf.
>>
>> I've got the replication working, but my only compliant is that I when I
>> tried to do a "Load data from master", I'd get an error message that
>> told me I was using  innodb tables, -but I'm not... I'll work on that
>> one later...
>>
>>
>> We've  been runnning full blast for over a week now and no-surprises. (
>> did I just jink myself or what?)  I was surprised to not find a lot more
>> issues.
>>
>>
>> :) Dave
>>
>>
>> -- 
>>
>> Open Source Information Systems, Inc. (OSIS)
>> Dave J. Hala Jr., President <dave at osis.us>
>> 641.485.1606
>>
>> _______________________________________________
>> ciapug mailing list
>> ciapug at cialug.org
>> http://cialug.org/mailman/listinfo/ciapug
>>
> 
>