Hi Jason,

<<
The change is the addition of the line "command.CommandTimeout = 0;"  If
this line is not present, then the default timeout is 15 second (I
think) and it way too short for the SQL commands that I run in my
script.  A better solution might be to have this as a attribute on the
<sql> task itself.
>>

I've just commited code to the CVS repository which makes CommandTimeout=0
the default, and added a "cmdtimeout" attribute to the sql task to change
this.

HTH,
--
Tomas Restrepo
[EMAIL PROTECTED]



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NAntContrib-Developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer

Reply via email to