Add a statement to the current SQL batch. You must call PrepareSqlBatch before you call AddStatement. If the number of parameters that will be added by using this statement will exceed the maximum number of allowed parameters in a single SQL batch, the statements that are already part of the batch will be executed, and then a new batch will begin with the statement that's being added.
Namespace: Microsoft.TeamFoundation.Framework.Server
Assembly: Microsoft.TeamFoundation.Framework.Server (in Microsoft.TeamFoundation.Framework.Server.dll)
Syntax
'Declaration
Protected Overridable Function AddStatement ( _
sqlStatement As String, _
parameterCount As Integer, _
allowExecute As Boolean, _
addStatementIndex As Boolean _
) As Integer
protected virtual int AddStatement(
string sqlStatement,
int parameterCount,
bool allowExecute,
bool addStatementIndex
)
protected:
virtual int AddStatement(
String^ sqlStatement,
int parameterCount,
bool allowExecute,
bool addStatementIndex
)
abstract AddStatement :
sqlStatement:string *
parameterCount:int *
allowExecute:bool *
addStatementIndex:bool -> int
override AddStatement :
sqlStatement:string *
parameterCount:int *
allowExecute:bool *
addStatementIndex:bool -> int
protected function AddStatement(
sqlStatement : String,
parameterCount : int,
allowExecute : boolean,
addStatementIndex : boolean
) : int
Parameters
sqlStatement
Type: System.StringSQL statement to add to the batch.
parameterCount
Type: System.Int32Number of parameters that will be bound after this statement.
allowExecute
Type: System.BooleanAllow execution of the partial batch if there are too many parameters.
addStatementIndex
Type: System.BooleanTreat statement as format string and replace "{0}" with zero-based statement index.
Return Value
Type: System.Int32
.NET Framework Security
- Full trust for the immediate caller. This member cannot be used by partially trusted code. For more information, see Using Libraries from Partially Trusted Code.