This second alpha release brings minor improvements and small fixes being the last version released this year. Some importing issues related to PostgreSQL 10 were fixed and now the users can import their databases without much problem. The diff tool was enhanced in such way that now is possible to compare two databases and not only a model and a database. There were some changes on the database design view like the ability to create relationships more easily and the ability to fade in/out the objects in the result set of the object finder tool. More details in the full post, good reading!

After one year and three months of hard work I proudly present you the pgModeler 0.9.0. This version does not bring extraordinary changes or improvements compared to the previous alphas and betas but it closes one more development cycle delivering an even more refined product to our users keeping the main purpose of this project in mind: create a quality open source software. In order to give an idea on how this project have changed since last year, or since 0.8.2, if we place together all change log entries from the beggining of the 0.9.0 development we would have: 175 entries being them 51 new features, 58 changes/improvements and 68 bug fixes. These numbers only indicates how this project is being constantly enhanced through the years. In this post I'll briefly describe what's new, don't miss it!

This release was meant to be the final 0.9.0 but due to the several changes, bug fixes and new features introduced it was more prudent to bring it as the second beta instead of the stable version so we could gather as many as possible feedbacks and fix any remaining issue in order to finally launch the pgModeler 0.9.0 stable. The new pgModeler brings lots of new features mainly related to the database modeling, but there are several changes and fixes in other areas of the software that will make it even more reliable and easy to use.

This is the last release before we can finally launch the stable 0.9.0. The development of this version was mainly focused on improving the user's experience on high resolution monitors by introducing an automatic machanism that is capable to resize dialogs, objects and fonts according to the current screen settings. This support is quite experimental and will be polished in the next releases. Another feature introduced was the support to browse the referenced rows as well the referrer rows in data manipulation dialog which will improve the the whole data handling experience. How these features work, their drawbacks and limitations are fully explained in this post. Don't miss it!

In this first beta release we have added some new design improvements as well important features and fixes that will improve the user's experience. Wishing to deliver as many as possible compatibility with all PostgreSQL releases of the series 9.x, we are bringing the support to indexes in materialized views which is supported by the RDBMS since the version 9.3. Another improvement added is the ability to edit object's source code (when applicable) in external editors of your choice. Now, turning to the data modeling field, the user is capable of toggle the displaying of the extended attributes area where indexes, rules, triggers and constraints are placed on tables and views. This can be useful to improve the visualization of huge models. Finally, other small improvements and fixes here and there were done making our pgModeler even more amazing. Checkout the details in the full post!

After almost four months of work we finally delivered important improvements in the design process that were requested long time ago as well several bug fixes that will make pgModeler even better to work with. If you follow the discussions in the Github community you're pretty aware that many enhancements are requested by our users. You also might know that one of the most awaited features in this project is the quick primary key creation, suggested at least 3 years ago. Well, this wait is over my friend because I'm proud to announce that this improvement is finally done! We also have introduced in this release: the object fading which will facilitate the model visualization, the ability to duplicate objects in the model, a better SQL history that is now persisted in its own file which is restored whenever the user connects to a database, and much more. In this post I will describe in details what this release have brought.