-
Notifications
You must be signed in to change notification settings - Fork 28
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
rendering more complex foreign keys #5
Comments
I have to check if there is a better way about not displaying duplicating columns in display (first issue).
You can check also implied references (
|
Thanks, that put me on the right track. It also turned out that some of my arrows were doubled because they were pointing to the wrong table. I've tried to make a minimal example of that. The following code solves both the composite key arrow problem in my sqlite case (which is a little hard to get into the minimal example) and the arrows pointing to the wrong table.
Interestingly, rearranging the input data solves the pointing to the wrong table problem as well, though not the general composite foreign key issue I had.
So this solves all of my problems at the moment. I hope you can incorporate it more directly. If you could also support sqlite in your package that would be a nice feature by the way. |
Similar problem from me and the following solved it as per @jessekps solution. dm2$columns = dm2$columns %>%
distinct(table, column, .keep_all=TRUE) Thanks both! Would be good to see a fix and potentially more symbols for tables with multiple foreign keys. Thanks again for thispackage! |
Hi,
thanks for the package, it has already been quite helpfull.
I have an sqlite database which I'm trying to model ( see code below ) but I'm having two small issues with more complex foreign keys.
kind regards,
Jesse
The text was updated successfully, but these errors were encountered: