Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "implicit" foreign keys #6

Open
kmpm opened this issue Oct 31, 2019 · 0 comments
Open

Support "implicit" foreign keys #6

kmpm opened this issue Oct 31, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@kmpm
Copy link
Contributor

kmpm commented Oct 31, 2019

This is definitely a feature request that should be possible to enable if wanted.

Sometime a DBA (or probably not trained DBAs) creates tables where the foreign keys are only defined in their imagination. This is a huge pain when working with legacy databases where everyone that has ever worked with it is no longer in the company.

It would be nice if schema-explorer could figure these out based on one or more strategies.
One such strategy would be that if a column have the same name and type in two different tables then they are related. Perhaps look for indexes where the column is the single primary key, that is probably the master table.

That way one could hopefully get a map of the database with, in some cases, reasonably correct relations.

Just a thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants