You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im not sure I think I might have found a bug with the CommandTimeout of QueryCommand in SubSonic 3 where the CommandTimeout can not be overriden.
Usage:
var sp = db.SpMyStoredProcedure();
sp.Command.CommandTimeout = 120;
sp.Execute();
However the stepping through the code I noticed the CommandTimeout of the DbCommand object that is created in the DbDataProvider in the following Methods is never set to the value within the QueryCommand.
As a short term solution I downloaded the source code and fixed this issue and another issue I was having and created my own DLL in the meantime. This has got me by while I'm waiting for the fix to be implemented
Lee
nathanb
added a commit
to nathanb/SubSonic-3.0
that referenced
this issue
Feb 14, 2019
Hi,
Im not sure I think I might have found a bug with the CommandTimeout of QueryCommand in SubSonic 3 where the CommandTimeout can not be overriden.
Usage:
var sp = db.SpMyStoredProcedure();
sp.Command.CommandTimeout = 120;
sp.Execute();
However the stepping through the code I noticed the CommandTimeout of the DbCommand object that is created in the DbDataProvider in the following Methods is never set to the value within the QueryCommand.
ExecuteReader(QueryCommand qry)
ExecuteDataSet(QueryCommand qry)
ExecuteScalar(QueryCommand qry)
ExecuteQuery(QueryCommand qry)
A possible fix to this would be the inclusion of:
cmd.CommandTimeout = qry.CommandTimeout;
Within each of the methods in the DbDataProvider.cs file, this fix has worked for me.
Thanks,
Lee Cooper
The text was updated successfully, but these errors were encountered: