I'm using MySQL 5.6.15 with Devart dotConnect 8.0.17. My LLBLGen version is 4.1 (November 26th, 2013).

dotConnect supports the attribute "Default Command Timeout" in the connection string. When I check the value of DaoClasses.CommonDaoBase.CommandTimeOut, the value is still the default 30 seconds. Wouldn't it be good to use the provided value in the connection string if available?

http://www.devart.com/dotconnect/mysql/docs/Devart.Data.MySql~Devart.Data.MySql.MySqlConnection~ConnectionString.html

That would indeed be convenient, though to my knowledge this is the first time I hear of a way to specify the command timeout in the connection string. In all other cases one can specify timeouts, but those are always for the connection itself, not for commands.

If you set the command timeout to 0 in your code, it won't be set in the dqe (so leaving the default the ado.net provider will set), so it should take the command timeout set in the connection string, as I assume the ado.net provider will set it when commands are assigned to a connection with the value from the connection string.

It seems to be part of the MySQLConnector for a while now. In de revision history of dotConnect there is no change message of a new parameter. It's just mentioned in the documentation.

Setting the command timeout in my code to zero, is the same as setting the command timeout to another value. I still have to do it in my code and I don't want to set this at multiple places. In some cases not every part of my code goes via the same route.

Anyways, it would be a nice feature to use the attribute value in the config file if provided.

Joop wrote:

It seems to be part of the MySQLConnector for a while now. In de revision history of dotConnect there is no change message of a new parameter. It's just mentioned in the documentation.

Setting the command timeout in my code to zero, is the same as setting the command timeout to another value. I still have to do it in my code and I don't want to set this at multiple places. In some cases not every part of my code goes via the same route.

No, I meant, you set it to 0 once and from then on you control it in the connection string in the config file of your application. So you can set it later on without recompiling if you want to. ]