- πΊπΈUnited States smustgrave
Since there hasn't been a follow up or movement going to close for now.
If still a valid bug please reopen verifying steps to reproduce.
Thanks all
I juste spent a few hours trying to figure out what was wrong but without success.
Given I have a field_interpretation_target
on a field_collection_item
, the base table of this field is not field_collection_item__field_interpretation_target
but something like field_collection_item__8283872305
(see \Drupal\Core\Entity\Sql\DefaultTableMapping::getDedicatedDataTableName
).
The thing is that, for some reason, Views keeps using the default table name so it leads to a fatal error:
field_interpretation_target:
id: field_interpretation_target
table: field_collection_item__field_interpretation_target
field: field_interpretation_target
relationship: field_interpretations_value
group_type: group
admin_label: Target
required: true
plugin_id: standard
Expected result: empty set of rows
Current result: fatal error (table does not exist)
After my investigation I found that something was happening in \Drupal\views\Plugin\views\relationship\RelationshipPluginBase::query
probably around $def['left_table'] = $this->tableAlias;
Figure out what's happening
Write a test to demonstrate the issue
Fix the problem
Review
Commit
Enjoy
None.
None.
None.
Closed: outdated
9.5
Last updated
Related to the Views in Drupal Core initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since there hasn't been a follow up or movement going to close for now.
If still a valid bug please reopen verifying steps to reproduce.
Thanks all