Page 1 of 1

TUniQuery.CommandTimeout

Posted: Thu 30 Aug 2018 12:37
by uffek
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.

Re: TUniQuery.CommandTimeout

Posted: Tue 12 Feb 2019 15:39
by MaximG
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.

Re: TUniQuery.CommandTimeout

Posted: Thu 14 Feb 2019 11:54
by uffek
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

Posted: Fri 22 Feb 2019 12:15
by MaximG
We will add the necessary description to our product documentation