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
The edges between tables are not rendered correctly using graphviz 9.0.0. The arrowtails are rendered, but the rest of the edge is cut off or missing completely.
Expected Behavior
The complete arrows should be rendered.
Alternatively, SchemaSpy/Graphviz version compatability should be documented clearly.
Current Behavior
SchemaSpy produces valid .dot but at incorrect .png, .svg and maybe more image formats.
Possible Solution
This might be a bug or breaking change in graphviz.
Steps to Reproduce (for bugs)
Install Graphviz 9.0.0
Run a valid SchemaSpy command.
Context
Database type (e.g. MySQL): mssql17
Database driver version (is you use a special one): mssql-jdbc-12.4.1.jre11.jar
Your Environment
Version used: 6.2.4
Operating System and version (e.g. Windows 10): Windows 10
The text was updated successfully, but these errors were encountered:
@npetzall
The last graphviz version before 9.0.0 was 8.1.0, which displays the correct behaviour.
SchemaSpy produces the same .dot file, and running e.g., dot example.dot -Tpng -o example.png results in the same unexpected behaviour. However, I don't know if its an intentional breaking change on their part or not. I've opened an issue in the Graphviz repo, so let's see how they respond.
The edges between tables are not rendered correctly using graphviz 9.0.0. The
arrowtails
are rendered, but the rest of the edge is cut off or missing completely.Expected Behavior
The complete arrows should be rendered.
Alternatively, SchemaSpy/Graphviz version compatability should be documented clearly.
Current Behavior
SchemaSpy produces valid
.dot
but at incorrect.png
,.svg
and maybe more image formats.Possible Solution
This might be a bug or breaking change in graphviz.
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: