pgModeler’s new release delivers 72 features, 93 improvements, and 74 fixes. Debugging capabilities now include dedicated log tabs for import and diff operations. The user can now visualize the SQL code from multiple selected objects. Relationships now generate indexes on foreign-key columns. The layer management now supports synchronizing visibility between tables and their relationships. Export operation can run transactionally for atomic DDL execution (except database and tablespace creation commands). The SQL editor's code completion now handles ALTER/DROP commands and ORDER BY columns. In the manage view, the handling form now uses a tabbed interface for better data visualization. The schema microlanguage supports escaped metacharacters and file includes. Data dictionaries can now be exported to Markdown format. The configuration files are now migrated more smoothly from prior major versions. The Plus edition adds plugins for quick constraint/index/relationship creation and query variable testing. The support for Qt 6.2 and 6.3 was dropped to simplify the codebase maintenance, and now Qt 6.4+ is required. Those and many other key changes are fully detailed in this post, so don't skip them!

After 4 months of work, I'm quite happy to announce another release of our beloved PostgreSQL database modeling tool! This version brings 23 new features, 22 improvements, and 14 fixes since the release of the previous alpha. This time, some important decisions were taken to make the code base a bit less complicated to maintain, at the same time some other portions of the tool were refactored to allow plugins' development to be more flexible. New features and important changes are also included, and I hope they will improve the tool's usage. Briefly speaking, this release introduces some nice features that can help in productivity. In the database modeling process, 1.2.0-alpha1 introduces a new way to quickly configure and assign layers to objects. The SQL export operation can be executed in a transaction block for atomic command executions, reverting changes if a single error occurs. In the SQL execution widget (in the management view), the code completion widget is now triggered for ALTER/DROP commands. Also, we're presenting the support for query variables which facilitates the test of queries using different variable formats adopted by ORMs. Finally, the data handling form received an important patch and now reunites the browsed tables in tabs drastically diminishing the use of standalone windows which could be confusing for the users. Everything will be fully explained in the full post, don't miss it!