Answers.Body: <p>For reference to anyone else that might have this problem. Some of the tables in my database did not have foreign keys in the specific Craft format. This occurred when table changes were done manually without knowing about this extra detail.
  Shout out to Brad Bell with Craft support for catching and fixing the problem.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-11T16:01:40.080Z
Answers.LastActivityDate: 2018-07-11T23:16:04.167Z
Answers.LastEditDate: 2018-07-11T23:16:04.167Z
Answers.UserDisplayName: Matt
Body: <p>Database Exception: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'n2-cr_matrixcontent_column1_locale_fk'; check that column/key exists</p>
  
  <p>This is the error I am receiving when attempting to update the database for the new version of craft. I've checked for that specific table and confirmed that it doesn't exist. How do I prevent it from trying to drop it or otherwise fix this problem?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-06T21:13:08.063Z
Comments.Text: Bump. Having a similar issue.
Comments.UserDisplayName: Dustin C
Tags: <craft3>
Title: Craft 2 -> 3 Upgrade Error
ThreadText: # Craft 2 -> 3 Upgrade Error
  
  (Asked by: username_0 on 2018-07-05)
  
  Database Exception: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'n2-cr\_matrixcontent\_column1\_locale\_fk'; check that column/key exists
  
  This is the error I am receiving when attempting to update the database for the new version of craft. I've checked for that specific table and confirmed that it doesn't exist. How do I prevent it from trying to drop it or otherwise fix this problem?
  
  **Tags:** craft3
  
  > **Comments:**
  > **username_1**: Bump. Having a similar issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-07-11. Score: 1
  
  For reference to anyone else that might have this problem. Some of the tables in my database did not have foreign keys in the specific Craft format. This occurred when table changes were done manually without knowing about this extra detail.
  Shout out to Brad Bell with Craft support for catching and fixing the problem.
  
  
  ---
  
  