Furthermore, PostgreSQL 9.x is gradually being ditched while modern versions are being quickly adopted, so it doesn't make sense to make pgModeler support such an old version of the database system since it is not maintained anymore by the community.īeing said that, pgModeler 1.0.0-beta will now refuse to connect to PostgreSQL servers below version 10. Honestly, it was a kinda relief for me because keeping a code base that embraces PostgreSQL 9.0 to 15 is a huge challenge because there are lots of syntax nuances that I need to keep track of which causes an increase in the code complexity. This move 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. Yes, pgModeler does not support PostgreSQL 9 anymore. 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 installed pgModeler 1.0.0-alpha before using 1.0.0-alpha or 1.0.0-beta you may get the error "Error while interpreting XML buffer at line 0 column 0. 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-beta.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |