Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It's always override by schema so not needed as part of field base.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | revert_unset_foreign_keys_2419479_5.patch | 852 bytes | florianmuellerch |
| #2 | 2419479-features-foreignkey-1.patch | 675 bytes | hefox |
Comments
Comment #2
hefox commentedComment #4
florianmuellerchThe applied patch (and the new version of features) results in an unchangeable state of "Overridden" by my features. If I revert the selected features, also the Foreign Keys gets reverted, but because they are unset with this patch, it's seen as a difference. Commenting out the unset line makes the features appear standard instead of overridden.
Is it critical having the foreign_keys still in the fields?
Comment #5
florianmuellerchUntil otherwise proven, this poses the possibility to comment out the unset statement.