For existing EntityReference User Reference fields from < 7.x-1.0-beta4, it appears possible to end up with corrupt field schemas even after the schema version is 7001. I've atatched a screenshot of the problem, showing the field_config data for an old, pre 7.x-1.0-beta4 user reference field, vs. a new 7.0-1.0-rc1 created user reference field.

Aas requested at #1491454: Alterations of EFQ needs to be made more robust, I've opened a new issue for this problem. The solution of ignoring the bundle filter setting if no foreign key set should work, given what's in the screenshot.

I'm still investigating and trying to reproduce how my schema got in this state. Curiously, my SQL storage database tables had been updated to the correct schema (ie. no field_foo_target_type column). My system table schema version was 7001, but the field_config row (shown in attached screenshot) was not updated. If I can reproduce that I"ll open a separate issue about it.

CommentFileSizeAuthor
entytreference-corrupt_old_userref_schema.jpg145.62 KBdamien_vancouver
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

damien_vancouver’s picture

damien_vancouver CreditAttribution: damien_vancouver commented

Please see #1518426: field_config settings for old User Reference fields from < 7.x-1.0-beta3 are still corrupt after entityreference_update_7001 - the patch there may alleviate the need for this fix.