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!

This release delivers some cool improvements to database modeling capabilities. The SQL source code editor has been upgraded with per-instance line wrapping controls and a built-in search/replace widget, centralizing these functions while removing redundant search implementations across the application. The debugging workflows are enhanced through dedicated output tabs in both database import and diff forms, providing clearer visibility into operations. When running in debug mode, the import form now remains open, allowing users to examine the executed commands and generated objects' code. The diff tool reintroduces the forced object re-creation option with added granularity - users can now select specific object types for re-creation through a dedicated popup menu in GUI. The SQL generation offers finer control by permitting disabled code segments to be included in output SQL scripts when needed. The extension objects received a better child object tracking (currently supporting types and schemas) and proper handling of custom schema names in managed data types. Those and some other user experience refinements are described in the full post.