Problem/Motivation

Follow up to #2282119: Make the Entity Field API handle field purging. When base fields are using shared storage, NULL values are allowed for the column they occupy. When copying to dedicated table storage for purging, NULL values are not allowed.

Proposed resolution

Only copy field values to dedicated storage if at least one column in the field schema is NOT NULL in the shared table storage.

Remaining tasks

User interface changes

API changes

Data model changes

Members fund testing for the Drupal project. Drupal Association Learn more

Comments

Sam152 created an issue. See original summary.

Sam152’s picture

Status: Active » Needs review
FileSize
927 bytes

This does the trick. Lets see if the existing tests pass.

Sam152’s picture

Issue summary: View changes
Sam152’s picture

Issue summary: View changes
amateescu’s picture

Oh wow, this is an interesting edge case..

Sam152’s picture

This test should expose this nicely.

amateescu’s picture

Status: Needs review » Reviewed & tested by the community

@Sam152++

The last submitted patch, 6: 2923572-6-TEST_ONLY.patch, failed testing. View results

  • larowlan committed 622d5c4 on 8.5.x
    Issue #2923572 by Sam152: Account for NULL base field values in shared...
larowlan’s picture

Status: Reviewed & tested by the community » Fixed

Committed as 622d5c4 and pushed to 8.5.x.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.