Adding new nodes or updating existing ones throws a fatal error, logging:

2015/07/02 12:43:00 [error] 424#0: *1975 FastCGI sent in stderr: "PHP message: Uncaught PHP Exception Drupal\Core\Entity\EntityStorageException: "SQLSTATE[42703]: Undefined column: 7 ERROR: column "revision_translation_affected" of relation "node_field_data" does not exist...

CommentFileSizeAuthor
#3 beta2beta-update-2453153--2521948-03.patch2.72 KBjhedstrom
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Corregidor’s picture

Corregidor CreditAttribution: Corregidor commented

My particular case is perhaps very simple, since my nodes haven't yet utilized either translations or multiple revisions. I simply added boolean "revision_translation_affected" columns to my node_field_revision and node_field_data tables and assigned false values for all nodes.

Solution is obviously more nuanced for those who actually experience the scenarios described in the issue.

vorapoap’s picture

vorapoap CreditAttribution: vorapoap commented

That "revision_translation_affected" is added in beta12 for both "node_field_data" and "node_field_revision"

I added it behind the sticky field 'tinyint(4) NULL'

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
CreditAttribution: jhedstrom at Phase2 commented
Version: » 8.x-1.x-dev
Status: Active » Needs review
FileSize
beta2beta-update-2453153--2521948-03.patch2.72 KB

The automatic schema update should add these when run during database update. However, for sufficiently old betas, exceptions that are thrown during this process prevent further schema updates from running, so while this works for beta11-12, it won't for beta10-12.

Attached is a test indicating the success for 11-12. It depends on the patch in #2511962: Upgrade path for 2509300 in order to pass.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
CreditAttribution: jhedstrom at Phase2 commented

I've committed #3 since it adds a valuable trait for other tests, and a nice addition to the runUpdates method. I'll leave this open for now, but in general if we tackle other schema changes that aren't automatic (eg, #2529554: Upgrade path for 1923406), then this one should work as expected without a manual update hook.

  • jhedstrom committed cb300c4 on 8.x-1.x 
    Issue #2521948 by jhedstrom: Upgrade path for 2453153
jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
CreditAttribution: jhedstrom at Phase2 commented
Status: Needs review » Active

  • jhedstrom committed 41dcc2d on 8.x-1.x 
    Follow-up to issue #2521948: Set starting beta to 8XXYY - 1 so 8XX00...
jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
CreditAttribution: jhedstrom at Phase2 commented
Status: Active » Closed (duplicate)

Once #2535082: Allow hook_update_N() implementations to run before the automated entity updates is committed this should be good.