Answers.Body: <p>Found solution. It's at the drupal complaint thread above :-) cheers! </p>
  
  <p>Here's a link to the relevant drupal upgrade complaint thread: <a href="https://www.drupal.org/project/drupal/issues/3052464" rel="nofollow noreferrer">https://www.drupal.org/project/drupal/issues/3052464</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-05-08T01:56:07.107Z
Answers.Text: This would be more acceptable as an Answer if it linked direct to the relevant comment in that drupal thread that contains the solution
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-05-07T20:39:23.640Z
Answers.LastActivityDate: 2019-05-13T16:00:51.777Z
Answers.LastEditDate: 2019-05-13T16:00:51.777Z
Answers.UserDisplayName: Neil P Davis
Body: <p>Don't do it yet. We had an issue where the drush updb failed. </p>
  
  <p><strong>A fresh install then drush updb did work</strong> but simply updating drupal and civicrm with composer then running drush updb left database in a state where it could no longer be updated by drush. </p>
  
  <p>I have no idea where the source of the issue is but the updb was complaining about null values in the database.</p>
  
  <p>We ran the drupal8/civicrm install from scratch then updated the db and it worked fine.</p>
  
  <p>Here's a link to the relevant drupal upgrade complaint thread:
  <a href="https://www.drupal.org/project/drupal/issues/3052464" rel="nofollow noreferrer">https://www.drupal.org/project/drupal/issues/3052464</a></p>
  
  <p>Luckily we try all of these things out in a mint copy of production vm first, before we actually do upgrades. This issue may or may not occur for you. Be careful!!!</p>
  
  <p>-Neil</p>
  
Tags: <drupal><upgrade>
Title: Cautionary Tale: Drupal 8.7.0 upgrade
ThreadText: # Cautionary Tale: Drupal 8.7.0 upgrade
  
  (Asked by: username_0 on 2019-05-07)
  
  Don't do it yet. We had an issue where the drush updb failed.
  
  **A fresh install then drush updb did work** but simply updating drupal and civicrm with composer then running drush updb left database in a state where it could no longer be updated by drush.
  
  I have no idea where the source of the issue is but the updb was complaining about null values in the database.
  
  We ran the drupal8/civicrm install from scratch then updated the db and it worked fine.
  
  Here's a link to the relevant drupal upgrade complaint thread:
  <https://www.drupal.org/project/drupal/issues/3052464>
  
  Luckily we try all of these things out in a mint copy of production vm first, before we actually do upgrades. This issue may or may not occur for you. Be careful!!!
  
  -Neil
  
  **Tags:** drupal, upgrade
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-05-07. Score: 1
  
  Found solution. It's at the drupal complaint thread above :-) cheers!
  
  Here's a link to the relevant drupal upgrade complaint thread: <https://www.drupal.org/project/drupal/issues/3052464>
  
  > **Comments:**
  > **username_2**: This would be more acceptable as an Answer if it linked direct to the relevant comment in that drupal thread that contains the solution  
  
  ---
  
  