Hi,
Just installed the latest version. There's a bug with the SQL Dialect.
In previous version, Connection.SQLDialect was used to set the dialect for the connection and after connecting, Connection.DBSQLDialect is the returned database dialect. However, in the most recent version, DBSQLDialect always returns '3'.
This is wrong.
This raises warnings in software I use with InterBase.
Please release an update.
With regards,
Martijn Tonies
SQL Dialect failure with latest version
Re: SQL Dialect failure with latest version
Hello,
Please specify exact version of your server.
Which dialect are you expecting to get, and which one do you actually get?
wbr, Oleg
DAC Team
Please specify exact version of your server.
Which dialect are you expecting to get, and which one do you actually get?
wbr, Oleg
DAC Team
Re: SQL Dialect failure with latest version
Tried on multiple server versions.
Connection.DatabaseInfo.DBSQLDialect seems to return the correct value and is different from Connection.DBSQLDialect.
Obviously, I was expecting '1' instead of '3'.However, in the most recent version, DBSQLDialect always returns '3'.
Connection.DatabaseInfo.DBSQLDialect seems to return the correct value and is different from Connection.DBSQLDialect.
Re: SQL Dialect failure with latest version
Hello,
We have reproduced and fixed the issue. This fix will be included in the next build of IBDAC.
wbr, Oleg
DAC Team
We have reproduced and fixed the issue. This fix will be included in the next build of IBDAC.
wbr, Oleg
DAC Team
Re: SQL Dialect failure with latest version
Hello!
We are excited to let you know that we have released new versions of DAC products with support for RAD Studio 10.4, which also include the latest fixes.
They are available for download on our website.
wbr, Oleg
Devart Team
We are excited to let you know that we have released new versions of DAC products with support for RAD Studio 10.4, which also include the latest fixes.
They are available for download on our website.
wbr, Oleg
Devart Team