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.
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
Comment | File | Size | Author |
---|---|---|---|
#6 | 2923572-6.patch | 1.77 KB | Sam152 |
#6 | 2923572-6-TEST_ONLY.patch | 887 bytes | Sam152 |
#2 | 2923572-2.patch | 927 bytes | Sam152 |
Comments
Comment #2
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedThis does the trick. Lets see if the existing tests pass.
Comment #3
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedComment #4
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedComment #5
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedOh wow, this is an interesting edge case..
Comment #6
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedThis test should expose this nicely.
Comment #7
amateescu CreditAttribution: amateescu for Pfizer, Inc. commented@Sam152++
Comment #10
larowlanCommitted as 622d5c4 and pushed to 8.5.x.