When comparing pgModeler vs SchemaSpy, the Slant community recommends SchemaSpy for most people. In the question“What are the best relational database design and modelling tools?” SchemaSpy is ranked 6th while pgModeler is ranked 10th. The most important reason people chose SchemaSpy is:
SchemaSpy can analyze database metadata in order to reverse engineer ER (Entity Relationship) diagrams for any JDBC-compliant database which includes Oracle, MySQL, Sql-Server and Postgres among others.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Diff scripts
Can generate scripts to synchronize a database.
Pro Reverse engineering
Can generate diagrams from an existing database.
Pro Export formats
Can export to SQL script file, PNG, SVG or directly to PostgreSQL.
Pro Entity Relationship Digramming for nearly any JDBC-compliant database
SchemaSpy can analyze database metadata in order to reverse engineer ER (Entity Relationship) diagrams for any JDBC-compliant database which includes Oracle, MySQL, Sql-Server and Postgres among others.
Pro Has a GUI option available
SchemaSpy is a CLI tool. For people who prefer GUI-based tools there's one available from a different maintainer which stands on top of the CLI version.
Cons
Con Compiling
Can't be compiled in Microsoft Visual Studio because of gcc/clang extensions.
Instructions on how to compile for Windows.
Con Does not work with schema dumpfiles
SchemaSpy has no methods for dealing with when you only have a schema generated via something like (mysqldump --no-data [options] >schema-only_dump.sql
) , and do not currently have access to a live database to connect with.
Con GUI option is a separate download by a different maintainer
Since the GUI version is from a different maintainer, it may be abandoned and eventually break if SchemaSpy development continues beyond that. Or it may implement new features much later than the CLI version.
Con Project may be dead or dying
The codebase on sourceforge hasn't seen an update since 2010.