Blog
Stay tuned with all pgModeler news
Multi-scene, orthogonal relationships, a complete Git client and a whole new look
It took more than a year, one alpha, one alpha1, one beta, and one beta1, but pgModeler 2.0.0 is finally stable. This is
the biggest release the project has ever had, with more than 850 commits since 1.2.3 alone, and this post tells the
whole story from 1.2.3 to today. The headline feature is multi-scene support: a model can now split its canvas into
scenes, by schema or by number of objects, so databases with thousands of tables stay fast to browse and edit.
Relationships can now be drawn with orthogonal lines routed around the tables, the new default. The whole
application was redesigned, from the logo and icons to a new theming engine, new fonts, and completely rebuilt
editing forms, and the interface can finally be translated, shipping with 34 languages including Brazilian Portuguese.
Import, Diff, Export, and Fix are now views of the main window. Diff can compare two models with no database at all. The SQL tool is more capable, PostgreSQL 18 temporal keys are supported, and SQL/XML generation is 50-70% faster
on real-world models. A long list of crashes and memory leaks is gone, saved connection and SSH tunnel passwords
are now encrypted, and a completely revisited user manual covers everyone from first-time users to plugin developers.
pgModeler now comes in two editions: Community stays free and open-source, and Plus adds import, diff, the SQL
tool, data handling, the database explorer, a complete Git client built right into the app, and a redesigned SSH tunnel
plugin. There are a couple of things to know before upgrading, like the new foreign key naming pattern. Grab a coffee;
this one is long, and I am proud of every line of it.
More stability and a full Git experience built right in
pgModeler 2.0.0-beta1 focuses on stability and refinement, fixing several crashes and memory leaks that could affect longer editing sessions, plus over a dozen smaller bug fixes across forms, exporting, and SQL completion. It also introduces a breaking change to the default foreign key naming convention, so models relying on the old pattern may need review after upgrading. The view editing form, layers panel, and command-line tool all get small usability upgrades, alongside visual polish for a more consistent interface across themes. The real highlight, though, is the versioning plugin in pgModeler Plus. What used to be a simple, disabled-by-default changelog for tracking partial diffs is now a full Git client built right into pgModeler — no more switching to the terminal or external GUI tools. The plugin supports cloning repositories, managing remotes, staging and diffing commits, pushing/pulling/syncing, guided conflict resolution, branch merging, cherry-picking, commit amending, reset and revert, tag management, stashing, and streamlined SSH and credential authentication. It's a complete Git workflow for teams and solo developers alike, now feature-complete ahead of the final 2.0.0 release.
Old site retirement, update in the pricing model and new pgModeler versioning
Do you remember that old fashioned, clunky and outdated web site? Say goodbye to it because today it is being officially declared RETIRED for the sake of all the people who follow this project since 2012 when pgModeler gained the world!
Now, If you were one of the persons who supported our beloved project by purchasing a download subscription in any moment between 2012 and today (January, 08), you sure remember the confusing monetization model, right? Forget it too... We have simplified it.
Finally, the software versioning schema will receive an important change starting this year for a good reason. In this post I'll give details about all I have done so far and what I have planned to this project.