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 modeling multi-table data, I've observed that real-world data often doesn't satisfy foreign key constraints. For example: parents_id=[1,2,3], children_id=[1,2], or parents_id=[1,2,3], children_id=[1,2,3,4].
I wish this tool could automatically assist me in cleaning the data, ensuring that foreign keys exist in both the parent and child tables (e.g., parents_id=[1,2], children_id=[1,2]).
In this way, the data used for multi-table simulation modeling can accurately reflect the associative relationships of foreign keys.
Proposed Solution
Retain only the intersection of foreign keys between the parent table and the child table.
$$ID_{remain} = ID_{parent} \Cap ID_{child}$$
Additional context
TBD
The text was updated successfully, but these errors were encountered:
@Z712023 I did some more looking around in the project, and I've found the single_table base class, would the solution for this issue be similar to this file?
Problem
When modeling multi-table data, I've observed that real-world data often doesn't satisfy foreign key constraints. For example:
parents_id=[1,2,3], children_id=[1,2]
, orparents_id=[1,2,3], children_id=[1,2,3,4]
.I wish this tool could automatically assist me in cleaning the data, ensuring that foreign keys exist in both the parent and child tables (e.g.,
parents_id=[1,2], children_id=[1,2]
).In this way, the data used for multi-table simulation modeling can accurately reflect the associative relationships of foreign keys.
Proposed Solution
Retain only the intersection of foreign keys between the parent table and the child table.
Additional context
TBD
The text was updated successfully, but these errors were encountered: