Command timeout always set to 30 seconds even if the connection timeout is larger.

[jluginbill]

The command timeout is always set to 30 seconds and there is no way to override this nor does it take the connection timeout into consideration Need to explicity set the cmd.CommandTimeout on the command object in the CreateCommand method with eiher a property or the connection timeout. This would allow for long running queries across a large database. I noticed when trying to delete 25,000 records it takes about 45 seconds to run but the petapoco timeout at 30 seconds because of the command object.

[toptensoftware]

Fixed in latest master branch - two new properties CommandTimeout and OneTimeCommandTimeout.

Leave both at zero for default time outs.
Set CommandTimeout to control the default timeout for all queries.
Set OneTimeCommandTimeout to control the timeout of just the next query.