Are there any plans to support Postgres 10?
What Postgres 10 feature you miss in Data Modeler?
Not a matter of features, it just generates an error saying cannot find libpg.dll and looks for it in the wrong path. I have copied the 32 bit version to the same folder as dm.exe, but still get the same error.
I don't think it's related to Postgres version, but I will do further tests here and let you know.
I get the same errors when trying to generate entities from Aurelius Connection using FireDAC. Works fine in Postgres 9, but not in 10.
Using Aurelius "generate entities" you get the error "cannot find libpg.dll"?!?!??
Sorry, that was the wrong error message - I have tried so many things - Connections from both Aurelius and FireDAC are successful. When trying to generate entities, error message: "EGUIException: Cannot find datatype: date range." Unfortunately, the accounting software database I am trying to connect to has many non-standard data types including hstore, jsonb, etc. If I could get Data Modeler to recognize a Postgres 10 database, I could exclude them from the Aurelius export. I have had a little success creating the database in V9, but some new data types generate errors in V9.
Making progress. Instead of just copying libpg.dll to the dm application folder, I copied the whole 32 bit bin folder. I can now get past the selection of PostgreSQL 9 or 11, but have a new error message. Data Modeler will not accept passwords for postgres user that contain spaces (I can work around this by changing the master password). This was a bug introduced in Delphi 10.3 with FireDAC. They have since fixed this bug in 10.3.1. I have sent 3 FireDAC units that were a quick fix that Embarcadero support sent me to fix the error via your TMS support email. Maybe it will be some help.
Changed my postgres password to not include spaces and Connection test succeeds. However, import database now fails with the same message that is displayed when using Aurelius Connection to generate entities: Cannot find datatype: daterange
For the record, after some private e-mail exchanges, the remaining issue is the daterange data type error. We will release a Data Modeler update that handles the issue.