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
I have tabulatr showing data directly from the underlying database tables with one table being a master table which works fine.
However, a key business requirement is to show records that are combined from physically separate tables that are similar in structure (e.g, id, name, created_at, updated_at fields for example) but represent different entities (e.g., oil_price_indexes, gas_price_indexes, etc.)
I had combined them in one parent table and differentiated each record based on the "type" of resource (oil, gas for example). Now I have to deal with a situation where a child table (e.g. contracts), can reference an oil_price_index or a gas_price_index. That makes it necessary for me to have TWO foreign keys from the combined table (price_indexes) in the child table which I do not think is a good relational design (I am using Postgres).
Kindly let me know what can and cannot be done using tabulatr under such circumstance.
Thanks.
Bharat
The text was updated successfully, but these errors were encountered:
I have tabulatr showing data directly from the underlying database tables with one table being a master table which works fine.
However, a key business requirement is to show records that are combined from physically separate tables that are similar in structure (e.g, id, name, created_at, updated_at fields for example) but represent different entities (e.g., oil_price_indexes, gas_price_indexes, etc.)
I had combined them in one parent table and differentiated each record based on the "type" of resource (oil, gas for example). Now I have to deal with a situation where a child table (e.g. contracts), can reference an oil_price_index or a gas_price_index. That makes it necessary for me to have TWO foreign keys from the combined table (price_indexes) in the child table which I do not think is a good relational design (I am using Postgres).
Kindly let me know what can and cannot be done using tabulatr under such circumstance.
Thanks.
Bharat
The text was updated successfully, but these errors were encountered: