I just recently ran across SchemaSpy as I'm working on rebuilding my PostgreSQL database structure. After a couple of initial mishaps with basic configuration and figuring out how to format the CLI command, I've been able to produce a great diagram of my new database. However, I noted that all of the tables listed in my analysis report are showing a value of "-1" in the Rows column. Going back through the command line output, I noted a number of lines that say:
My schemas and tables are created using mixed-case names (because I'm weird like that), but it appears that SchemaSpy is not using it as mixed-case in the fetchNumRows function. I've tried it both with and without double-quotes around the original schema name, but both give me the same result. I even tried it with single-quotes around the schema name, but that gave me the following error:
No tables or views were found in schema ''<SchemaName>''.
The schema does not exist in the database.
Make sure that you specify a valid schema with the -s option and that
the user specified (<username>) can read from the schema.
Note that schema names are usually case sensitive.
As an example, if I have a schema called "Company", I set the -s parameter in my command line to read:
I just recently ran across SchemaSpy as I'm working on rebuilding my PostgreSQL database structure. After a couple of initial mishaps with basic configuration and figuring out how to format the CLI command, I've been able to produce a great diagram of my new database. However, I noted that all of the tables listed in my analysis report are showing a value of "-1" in the Rows column. Going back through the command line output, I noted a number of lines that say:
The <schemaname> listed is an all lower-case representation of the schema name I supplied in my command line arguments:
My schemas and tables are created using mixed-case names (because I'm weird like that), but it appears that SchemaSpy is not using it as mixed-case in the
fetchNumRows
function. I've tried it both with and without double-quotes around the original schema name, but both give me the same result. I even tried it with single-quotes around the schema name, but that gave me the following error:As an example, if I have a schema called "Company", I set the
-s
parameter in my command line to read:But, in the warning, it shows it as lower-case:
One thing to note is that it DOES have the correct mixed-case name of the table name. It's only the schema name that's converted to all lower-case.
Last edit: G_Hosa_Phat 2017-11-29