Related explorer now iteratively walks over the objects which completely follows the schema. This is the academic approach. It might be beneficial to have a shortcut. In similar fashion for the creation of the embedded table create a references table which follows the same pattern: a parent object, and a source object that refers to the parent.
This must be more naively implemented than embedded, meaning it would actually show parent to parent relationships, and not embedded child to parent relationships. So the relationships are at first class object level, and this will cause some deduplication issues. So the references must be deduplicated per parent object, and only then written to the table.
Once this is in place exporting data should take in consideration these reference table, so we know a priori that in fact we have some extra objects to add to the output (or would have to prune it).
Split the academic code from related explorer so we can always do it correctly and validate against the shortcut output.
The reference table is able to assist with inward references.
skinkie
commented
1 month ago
Related explorer now iteratively walks over the objects which completely follows the schema. This is the academic approach. It might be beneficial to have a shortcut. In similar fashion for the creation of the embedded table create a references table which follows the same pattern: a parent object, and a source object that refers to the parent.
This must be more naively implemented than embedded, meaning it would actually show parent to parent relationships, and not embedded child to parent relationships. So the relationships are at first class object level, and this will cause some deduplication issues. So the references must be deduplicated per parent object, and only then written to the table.
Once this is in place exporting data should take in consideration these reference table, so we know a priori that in fact we have some extra objects to add to the output (or would have to prune it).
Split the academic code from related explorer so we can always do it correctly and validate against the shortcut output.
The reference table is able to assist with inward references.