Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Failed: Drupal\Core\Entity\EntityStorageException: Exception thrown while performing a schema update. MySQL needs the 'parent_type' field specification in order to normalize the 'paragraphs__parent_fields' index in Drupal\Core\Entity\Sql\SqlContentEntityStorage->wrapSchemaExcephttps://www.drupal.org/project/paragraphs/issues/2833935#comment-1347194...() (line 1615 of /Applications/MAMP/htdocs/oasdrupal2020/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).
Screenshot:
Comment | File | Size | Author |
---|---|---|---|
#23 | interdiff_14_23.txt | 366 bytes | bserem |
#23 | 3114512-23.patch | 1.01 KB | bserem |
#14 | 3114512-14.patch | 1.01 KB | jdleonard |
| |||
Screenshot 2020-02-19 at 12.29.36 PM.png | 202.1 KB | isalmanhaider |
Comments
Comment #2
LRoelsI had the exact same thing today. I noticed that the same db update was performed in 8021. I wrote a patch for my environment that skipped 8017 since the update of 8021 seems to work.
Comment #3
Byrongary CreditAttribution: Byrongary commentedWhat was the patch that you wrote?
Comment #4
julien CreditAttribution: julien as a volunteer commentedAdding patch. see duplicate https://www.drupal.org/project/paragraphs/issues/2833935#comment-13471948
Comment #5
Brian Weaver CreditAttribution: Brian Weaver commentedWe encountered this MySQL error when trying to update from 1.6 to 1.11 on Pantheon. Applying the #4 patch enabled all the updates to apply.
Comment #6
esolitosI can confirm that patch provided in #4 works as expected.
Comment #7
rkdesantos CreditAttribution: rkdesantos as a volunteer commentedI can also confirm the patch works as expected.
Comment #8
esolitosComment #9
MetalG CreditAttribution: MetalG commentedIf i'd just wait a bit with upgrading, will this issue be solved anyway?
Comment #10
Ghost of Drupal PastAnother confirmation this works.
Comment #11
Siavash CreditAttribution: Siavash commentedWorked! Thanks.
Comment #12
Les LimWhy does the patch in #4 create a new update hook
paragraphs_update_8023()
when there's alreadyparagraphs_update_8021()
that does the same?Comment #13
MetalG CreditAttribution: MetalG commentedDidnt work for me btw.
Comment #14
jdleonardLike #12, I don't understand why the patch in #4 implements an additional hook. Patch without the additional hook attached.
Comment #15
julien CreditAttribution: julien as a volunteer commentedSee duplicate. https://www.drupal.org/project/paragraphs/issues/2833935#comment-13471948
Comment #16
jdleonard@julien, I'm confused. Are you explaining why the patch in #4 implements
paragraphs_update_8023()
when the same logic already exists inparagraphs_update_8021()
? If so, I don't follow.Comment #17
julien CreditAttribution: julien commentedThe patch was just done to pass the updates without hook_update stack execution issue. It is maybe not the right way to achieve it but had to pass the hook_updates without errors for now.
Comment #18
Les LimJust a note that it's not a good idea to apply uncommitted update hook patches on a production site. If another release comes out, it may be using the same hook_update_N() function for a different update, and you will miss it because your patched version has already advanced past that update hook's schema number.
Comment #19
plousia CreditAttribution: plousia commentedPatch in #4 worked for me, #14 did not.
Comment #20
julien CreditAttribution: julien commented@plousia thanks
Comment #21
laurenmzPatch in #14 worked for me, noting that the comment should read "Moved function content to paragraphs_update_8021()." if another hook_update_N() isn't being added.
Comment #22
Phonoman CreditAttribution: Phonoman commented#14 is the way to go even though there's the 802
3comment typo when it's really moved to 8021 as @laurenmz noted.Comment #23
bserem CreditAttribution: bserem at zehnplus commentedPatch worked fine for me.
I also fixed the typo in the comment, see attached file.
I will mark this as RTBC, since my patch changes nothing actually.
Comment #24
bserem CreditAttribution: bserem at zehnplus commentedComment #25
phjouPatch #4 worked for me, not #14. Same as #19
Comment #26
GiorgosKUpdating core from 8.6 to 8.8 gave me lots of the original error messages on
drush updb
Tried #23/#14 but gave the same error. #4 worked,
Comment #27
PhoenixAvenger CreditAttribution: PhoenixAvenger commentedI was updating a site that had not been updated in a LONG time and encountered this problem. What worked for me was first updating Paragraphs to 1.7 then updating to 1.11 rather than updating directly to 1.11
Comment #29
BerdirLooks like this is something that people might hit if they update from a schema version between 8013 and 8017, before 8013 now has passing test and this doesn't break them, so also committing this. Did update the comments a it, because this wasn't and would create a mess on drush updb.