** pgModeler 0.8.0 is out! **
After eight months working on create an even more improved product the final 0.8.0 is done. This version is the best one ever created because the software is more stable, reliable, useful and beautiful.
Compared to the previous release (0.7.2) this one has a lot more features that will surely improve the database design. Also, there are new features to help user in manage live databases.
To give an idea on how pgModeler has changed since 0.7.2, the full change log for the new release has 349 entries, being 85 new features, 147 changes and 117 bug fixes. Detailed changes available on CHANGELOG.md.
Obviously, not all new features or changes will be noted since they were created to help in bug fixes but what matters is that pgModeler is now a better product.
Some key features of this new version are:
1) Optmized layout: the entire layout was improved, separating portions of the software in form of views (welcome, design and manage) giving users a better usage experience. Also, as part of layout improvements, the database model objects are now more clean and smooth being more pleasing to the eyes.
2) Faster code generation: the SQL and XML code generation speed was increased by introducing the cached code feature. With this feature the loading, saving and export processes are more faster speeding up the productivity.
3) Per-user configurations: pgModeler now is capable to store its settings separated for each user in the same system. This is quite handy when several users need to run the software with their own preferred settings without mess with others settings.
4) Model database diff: create SQL scripts containing all commands needed to keep synchronized both model and database. With the diff feature you can make changes on a living database without drop it and recreate from the model that originate it. Just do the needed changes on the model and compare it to the database, pgModeler will handle the rest creating DDL commands and storing them on a file or applying directly to a server. NOTE: this is an experimental feature so it may fail in some cases.
5) Improved reverse engineering: the import process is even better. Free from a lot of bug of previous releases the import permits user to create partial models by importing only a few set of objects or the entire database as he wishes. This process now is capable to solve automatically the majority of problems related to object's dependencies that previous versions could not handle.
6) Improved SQL tool: being now a dedicated section of the software the SQL tool (manage view) is even better. Now its possible to handle several databases, manage table data through the data manipulation dialog and run SQL commands directly on the server. In this release, SQL code snippets were introduced in order to help users to create and execute SQL commands when working on a database.
7) Improved model validation: the main source of crashes in previous releases the validation process was carefully improved being more stable and reliable by fixing the majority of model inconsistencies that may appear during the design time.
8) Improved model export: several bugs were fixed on the model export process. Additionally, user now have the option to run DROP commands before create an object directly on the database. This is useful when you do not want to drop the entire database in order to recreate the objects.
9) Miscellaneous: several bug fixes throughout the subprojects, ability to drop objects in cascade way during design, several improvements on quick actions menu when two or more objects are selected, several improvements on the configuration sections and much more.
So, what comes next?
First, the author will go on a vacation to refresh his mind! Emoticon smile
Second, the user's guide will be completely updated to include new features of release 0.8.0.
Finally, the project's site will be completely redesigned.
I'm not planning to release any patch version in the next 30-45 days but if some severe bug is discovered I'll not hesitate in implement a fix and release it. But if the bug is a simple one I prefer to be focused on the tasks mentioned before.
I really proud of this work and I hope will all like it! Emoticon wink