Hi Brendon, You're welcome.
"is there a document anywhere that outlines cautions one should take note of when upgrading?" There's usually release notes that describe changes, but upgrades of 3rd party software are often skipping multiple versions and these changes can be hidden away in very long apendices. Many years ago when I was a PL/I and Cobol programmer I learned to avoid conflict with the fact that half the dictionary was "reserved" by applying the rule never use an English language word as a variable name. It doesn't apply as much in these days of less verbose languages, but I tend to avoid using common English words as column names ... I never know when database-X is going to become important to us and my SQL is going to break. With MySQL you can always quote column names. Some say you should always do this, I'm not keen on it as it makes migrating to other database software more difficult. Bruce On Tue, Aug 10, 2010 at 12:27 PM, Brendan Brink <[email protected]> wrote: > Thank you so much Bruce, took your advice and worked.... > > is there a document anywhere that outlines cautions one should take > note of when upgrading? > > be good to prevent errors before they pop up out of the blue... > > Thanks again Bruce - life saver! > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] > -- Bruce Clement Home: http://www.clement.co.nz/ Twitter: http://twitter.com/Bruce_Clement Google Buzz: http://www.google.com/profiles/aotearoanz "Before attempting to create something new, it is vital to have a good appreciation of everything that already exists in this field." Mikhail Kalashnikov -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
