Is it possible to add keyword "Command Timeout" to the connection string

[Georgy-Losenkov]

Right now the only way to override default value of SqlCommand.CommandTimeout is to do this in code.
It would be nice to do this through connection string/ConnectionStringBuilder/Connection.

[cheenamalhotra]

Hi @Georgy-Losenkov

I believe it should be possible, we'll keep that noted for future enhancements.

[roji]

For reference, Npgsql has this.

[ErikEJ]

Would you consider a community PR for this?

[ErikEJ]

@roji Can you point me to how you are prioritizing CommandTimeout set via the Connection string vs CommanTimeout set in code?

[roji]

In Npgsql, the programmatic NpgsqlCommand.CommandTimeout takes precedence over the connection string parameter - as a general rule, programmatic access always overrides connection string parameters (as they can be more specific).

[ErikEJ]

@roji Thanks! Will try the same with SqlCommand. Nice #regions 😁

[ErikEJ]

API proposal:

SqlConnectionStringBuilder: public int CommandTimeout { get; set; }

SqlConnection: public int CommandTimeout { get; }

SqlCommand will use same precedence logic as here

[cheenamalhotra]

Would you consider a community PR for this?

@ErikEJ That would be great!
As for us, it isn't in the top priority list as of now.

[ErikEJ]

I will look into it, I think it would be a very welcome addition, in particular if you are using some library on top of ADO.NET, where it may not be possible for you as a library consumer to modify the command timeout.