Right now the PostgreSqlConnectionProvider throws an exception:
System.ArgumentException: Keyword not supported: encoding
Parameter name: keyword
This is because the connection string keyword "encoding" is obsolete in Npgsql 3.0.1 (see http://www.npgsql.org/doc/migration-3.0.html)
Update PostgreSqlConnectionProvider to reflect breaking changes introduced in Npgsql 3.0.1
Answers approved by DevExpress Support
created 9 years ago
(modified 9 years ago)
We have implemented the functionality described in this ticket. It will be included in our next update(s).
Please check back and leave a comment to this response to let us know whether or not this solution addresses your concerns.
- v15.2.4Download Official Update
- v15.1.8Download Official Update
Show previous comments
(3)
Hello Philippe,
To process your recent post more efficiently, I created a separate ticket on your behalf: T297300: How can I intercept the connection string created by the wizard. This ticket is currently in our processing queue. Our team will address it as soon as we have any updates.
Hi
this seems to be still the case for XPO 20.2.3
The following:
C#class Program
{
static void Main(string[] args)
{
Console.WriteLine(typeof(PostgreSqlConnectionProvider).Assembly.GetName().Version + ": "+ PostgreSqlConnectionProvider.GetConnectionString("server","userid", "password", "database"));
}
}
Prints:
Code20.2.3.0: XpoProvider=Postgres;Server=server;User Id=userid;Password=password;Database=database;Encoding=UNICODE;
Hi,
The GetConnectionString method does not remove the Encoding parameter. We didn't change it. The CreateProviderFromString method removes this parameter from a connection string.
Thank you for your report. Our developers will research this issue.