Re: CommandTimeout for ExecuteNonQuery seems to be duplicated

[Jose Gabriel Valencia Ornelas]

Hi

You can check the documentation about the Command and the Command timeout, the timeout is not a representation directly of the time elapsed during the execution of the command, since Connector 6.2 the behavior was changed.

https://dev.mysql.com/doc/connector-net/en/connector-net-programming-mysqlcommand.html

this is an extract at the end of that document

MySQL Connector/Net 6.2 introduced timeouts that are aligned with how Microsoft handles SqlCommand.CommandTimeout. This property is the cumulative timeout for all network reads and writes during command execution or processing of the results. A timeout can still occur in the MySqlReader.Read method after the first row is returned, and does not include user processing time, only IO operations. The 6.2 implementation uses the underlying stream timeout facility, so is more efficient in that it does not require the additional timer thread as was the case with the previous implementation.

Hope this helps