Errors generated by custom indexing during upgrades
Posted: Fri Nov 19, 2010 1:10 pm
We just upgraded one of our development servers from 7.0.4 to 7.0.5 and encountered one alter table error. The cause of the error looks to be indexes we created for improved performance. I deleted the index and ran the alter command. The site looks OK.
This makes me wonder if it would be reasonable to expect future errors as a result of the indexes we've created. NOTE: IMO, additional custom indexes are a necessary part of AC performance tuning.
If fields are being dropped during upgrades, would it be reasonable (and safe) to have AC drop any indexes referencing those fields? That would eliminate these errors in the future.
AC people, could you weigh in here please? Is this something that could or should be done during upgrades?
This makes me wonder if it would be reasonable to expect future errors as a result of the indexes we've created. NOTE: IMO, additional custom indexes are a necessary part of AC performance tuning.
If fields are being dropped during upgrades, would it be reasonable (and safe) to have AC drop any indexes referencing those fields? That would eliminate these errors in the future.
AC people, could you weigh in here please? Is this something that could or should be done during upgrades?