Summary
While all the fields are generally useful, and avoiding foreign keys makes it easy to load large volumes of data for migration or archiving purposes, it means you cannot generate useful ERDs from the schemas.
Please describe the problem you are trying to solve.
Tools that try to generate ERDs from Salesforce don't have a guessing mechanism like we have here, and often include a lot of unneeded details. To create useful ERDs a simplified version of the objects in a database with all the needed foreign keys would be useful.
Proposed Solution
Have a mode to generate tables with foreign keys, but no other fields (just lookups and M/D fields from Salesforce). The keys probably should be driven from a setting in the preferences, but this problem likely benefits from a mode switch at the end of the process.
Summary
While all the fields are generally useful, and avoiding foreign keys makes it easy to load large volumes of data for migration or archiving purposes, it means you cannot generate useful ERDs from the schemas.
Please describe the problem you are trying to solve.
Tools that try to generate ERDs from Salesforce don't have a guessing mechanism like we have here, and often include a lot of unneeded details. To create useful ERDs a simplified version of the objects in a database with all the needed foreign keys would be useful.
Proposed Solution
Have a mode to generate tables with foreign keys, but no other fields (just lookups and M/D fields from Salesforce). The keys probably should be driven from a setting in the preferences, but this problem likely benefits from a mode switch at the end of the process.