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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: