I am on Mysql 5.067. I run a site with Drupal and Civicrm and I am trying to upgrade Civicrm now. This however fails, and I have the impression that this is because of the fact that some of the old Civicrm tables are locked with Foreign Key Constraints.
I was told to use SET FOREIGN_KEY_CHECKS=0;
drop everything (reupload and upgrade
SET FOREIGN_KEY_CHECKS=1;
This however does not work and the reason for that may be the fact that the Foreign Keys for both my Drupal and my Civicrm tables (as well as Primary and Unique keys) are stored in a table called Table Constraints which is part of a separate database called Information Schema.
Now I do not know what to do: simply remove those 250 records that define the Constraints for Civicrm in that Constraints Table? Maybe, but do I not lose the links to whatever these keys are foreignly linked? And if I remove them? how do I get them back later, since the backup only has the data for Civicrm and ignores the information schema (it might be that the upgrade script takes care of that. Any advice is most welcome!
I was told to use SET FOREIGN_KEY_CHECKS=0;
drop everything (reupload and upgrade
SET FOREIGN_KEY_CHECKS=1;
This however does not work and the reason for that may be the fact that the Foreign Keys for both my Drupal and my Civicrm tables (as well as Primary and Unique keys) are stored in a table called Table Constraints which is part of a separate database called Information Schema.
Now I do not know what to do: simply remove those 250 records that define the Constraints for Civicrm in that Constraints Table? Maybe, but do I not lose the links to whatever these keys are foreignly linked? And if I remove them? how do I get them back later, since the backup only has the data for Civicrm and ignores the information schema (it might be that the upgrade script takes care of that. Any advice is most welcome!