You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we're fetching values for a table, we're also adding all the all-outbound paths that the page needs to the same request. This list is computed as part of the Reference.activeList API. In this API, we go over all the different ways that an all-outbound path might be needed (visible columns, wait_for of visible columns, and fkeys in the source-definition).
To ensure we're not adding duplicate join statements, we're adding each unique path only once. This uniqueness check is done by checking the name property, which is populated based on the whole path, including the last column. But the last column doesn't affect the generated request in' entity' paths, so we should only look for the foreign key hops in this case.
The text was updated successfully, but these errors were encountered:
RFSH
changed the title
Fix the duplicate detection for entity all-outbound paths
Improve the duplicate detection for entity all-outbound paths
Feb 5, 2024
When we're fetching values for a table, we're also adding all the all-outbound paths that the page needs to the same request. This list is computed as part of the
Reference.activeList
API. In this API, we go over all the different ways that an all-outbound path might be needed (visible columns,wait_for
of visible columns, andfkeys
in thesource-definition
).To ensure we're not adding duplicate join statements, we're adding each unique path only once. This uniqueness check is done by checking the
name
property, which is populated based on the whole path, including the last column. But the last column doesn't affect the generated request in' entity' paths, so we should only look for the foreign key hops in this case.The text was updated successfully, but these errors were encountered: