AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pgmodeler mac12/31/2023 ![]() Honestly, it was a kinda relief for me because keeping a code base that embraces PostgreSQL 9 to 15 is a huge challenge because there are lots of syntax nuances that I need to keep track of, which causes code complexity to increase. My goal is to make the code Qt 6 compliant only! Goodbye PostgreSQL 9.x and hello PostgreSQL 15!ĭropping PostgreSQL 9.x support was delayed a lot of times since the launching of PostgreSQL 10, so I decided that during the development of pgModeler 1.0.0 the support for discontinued versions of the RDBMS would be completely dropped, and that was done. Due to the amount of time that pgModeler takes from me, I don't intend to make the code work on both Qt 5 and 6. Surprisingly, after moving to Qt 6, the code still builds on Qt 5.15.x but bear in mind that there can be backward compatibility breaking at any time as soon as new features are introduced to Qt 6 exclusively and they are used by pgModeler. There is still some work to do to finish the full migration but I can say for sure that the current state of the code is pretty stable and works satisfactorily well. ![]() The main challenge, which took more time, was to move the huge amount of deprecated code related to Qt 5.15.x to the newer API introduced by Qt 6 without breaking things. To be more specific, the code builds fine on Qt 6.2.x, 6.3.x, and 6.4.x. It gave me some headache but now pgModeler is fully compatible with Qt 6, taking advantage of all advances that this major framework version brought. After erasing the files, start pgModeler again so the erased files can be created again by the tool. config/pgmodeler-1.0 (Linux), C:\Users\(user)\AppData\Local\pgmodeler-1.0 (Windows), /Users/(user)/Preferences/pgmodeler-1.0 (macOS). The solution is to manually erase the files *nf in your user's local storage where pgModeler settings are saved: /home/(user)/. This error occur due to an attribute of the syntax highlight files which was dropped. Message generated by the parser: No declaration for attribute partial-match of element group." right before pgModeler quits during its startup. If you have installed pgModeler 1.0.0-alpha before and skipped versions 1.0.0-alpha1 and above you may get the error "Error while interpreting XML buffer at line 0 column 0. Here go some key changes and improvements related to this version! Before you start using 1.0.0! This release brings tons of changes, fixes, and new features compared to 0.9.4 and I already consider the best pgModeler ever! I'm really looking forward to receiving all kinds of feedback. From now on, my focus will be completely on 1.0.0. With this announcement, I declare retired pgModeler 0.9.4, which implies that no more support will be provided to it. ![]() Oh boy! I thought this moment would never come, but it's finally here! pgModeler 1.0.0 is a reality, a dream of seventeen years, and a huge effort to deliver a useful product to the open-source community. ![]() This way, at the first start of the newer version, some settings will be automatically migrated if the tool detects the configuration files related to 0.9.4 or below in the system! Attention: pgModeler 0.9.x settings are not compatible with pgModeler 1.0.0.
0 Comments
Read More
Leave a Reply. |