For MSSQL the default value of TUniQuery.CommandTimeout is 0, for PostgreSQL it is listed as a property, but with no default value and for Oracle it is not listed at all.
Can someone expand on this for PostgreSQL and Oracle.
TUniQuery.CommandTimeout
Re: TUniQuery.CommandTimeout
Indeed, you can use the TUniQuery.CommandTimeout property when working with SQLServerUniProvider and PostgreSQLUniProvider. We will consider the support for this property when using OracleUniProvider.
You can leave your suggestions at our UserVoice page ( https://devart.uservoice.com/forums/104 ... 939-unidac ), and if there are many votes for your suggestion, we will implement it.
You can leave your suggestions at our UserVoice page ( https://devart.uservoice.com/forums/104 ... 939-unidac ), and if there are many votes for your suggestion, we will implement it.
Re: TUniQuery.CommandTimeout
My suggestion was really about describing the current status in the documentation for all providers. It wasn't about implementing any new features.
Re: TUniQuery.CommandTimeout
We will add the necessary description to our product documentation