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

columns #957

Open
spireitepaul opened this issue Sep 7, 2022 · 1 comment · May be fixed by #1035
Open

columns #957

spireitepaul opened this issue Sep 7, 2022 · 1 comment · May be fixed by #1035

Comments

@spireitepaul
Copy link

spireitepaul commented Sep 7, 2022

Running the Docker version of Schemaspy against SQLServer databases.

I expect all tables in the Relationship diagram to show all columns

Current Behavior

some render a row containing just three dots (...)
some render two columns, and a third row of three dots

Steps to Reproduce (for bugs)

Just running the standard build process.

Context

Readers of the schema diagram expect to see all columns in the relation diagrams

  • Database type SQLServer

  • Database driver version 9.4

  • Full command including arguments how you run SchemaSpy:
    docker run -v "/tmp/ssdata:/output" -v "$(Build.SourcesDirectory)/connproperties/schemaspy.properties:/schemaspy.properties" -v "$(Build.SourcesDirectory)/driver/sqljdbc_9.4/enu:/drivers" schemaspy/schemaspy:snapshot -p $(SQL_P) -u $(SQL_U) -db $(DBName) -norows -maxdet 400

Your Environment

This in an Azure Devops pipeline, ubuntu-image
Agent name: 'Hosted Agent'
Agent machine name: 'fv-az414-677'
Current agent version: '2.210.0'
Operating System
Ubuntu
20.04.4
LTS

Is there any way I can force all columns to be rendered?

@npetzall
Copy link
Member

-maxdet is the way to force it, but it might be stupid now that I look at it.

It's not the number of tables, but combined number of tables and views.
So you might need to go even higher than 400.

npetzall added a commit to npetzall/schemaspy that referenced this issue Mar 6, 2023
@npetzall npetzall linked a pull request Mar 6, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants