This question is in reference to Atlassian Documentation: MySQL Collation Repair: Table Level Changes
Example:
ALTER TABLE `CONTENT` MODIFY `CREATOR` varchar(255) CHARACTER SET UTF8 COLLATE utf8_bin;
ERROR 1832 (HY000): Cannot change column 'CREATOR': used in a foreign key constraint 'FK_CONTENT_CREATOR'
You can disable the constraints checks, run the ALTER statement and then enable the constraint checker again:
SET foreign_key_checks = 0; ALTER TABLE `CONTENT` MODIFY `CREATOR` varchar(255) CHARACTER SET UTF8 COLLATE utf8_bin; SET foreign_key_checks = 1;
See if it helps...
Thank you Guilherme. Got my service up an running again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome, buddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you guy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The above solution is not recommended on production though. You can try locking table before executing your commands and finally unlocking it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply and helped me solve the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.