-
Notifications
You must be signed in to change notification settings - Fork 306
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
Relationship between Unique Keys and Foreign Key #1430
Comments
Can someone pls help |
Could you supply a small example with just two tables and how the relationship is declared. Implied won't find it I think, it only looks at PK. But we do ask the jdbc driver for imported and exported columns/keys. For me to look into this I also need to know the version of Oracle and driver so that I'm sure to reproduce the issue. Then I can check different driver if they allow this else we might consider expanding the implied to check on both PK and UQ indexes. |
Version of Oracle is 19.14 |
Would you be able to supply Sql statement to produce this kind of relationship. I'm gonna check if there is any filtering applied if a FK is returned but it doesn't reference a PK. Because |
I'll need some additional time to look into this, since I find the Oracle 19 container images for M1 a little sketchy since I can't find a release to download of the software for M1(arm64). I'll need to have time to sitt at a different computer. |
Expected Behavior
Oracle allows to build child-parent relation between Unique-Key and FK.
SchemaSpy is working fine for the relationships defined between Primary Key and Foreign Key.
In our organization we have defined some relations between Unique Keys and Foreign Key. (where unique key column is parent and other one being child)
Current Behavior
SchemaSpy reconize relations only between PK and FK, not UK and FK
Possible Solution
Is there any way I can make SchemaSpy to consider such constraints as well and show lines in relationship tab?
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: