Assembly: System.Data.OracleClient (in system.data.oracleclient.dll)
'Declaration Public Overrides Property CommandType As CommandType 'Usage Dim instance As OracleCommand Dim value As CommandType value = instance.CommandType instance.CommandType = value
/** @property */ public CommandType get_CommandType () /** @property */ public void set_CommandType (CommandType value)
public override function get CommandType () : CommandType public override function set CommandType (value : CommandType)
Property ValueOne of the CommandType values. The default is Text.
When the CommandType property is set to StoredProcedure, you should set the CommandText property to the full Oracle call syntax. The command then executes this stored procedure when you call one of the Execute methods (for example, ExecuteReader or ExecuteNonQuery).
The Connection, CommandType and CommandText properties cannot be set if the current connection is performing an execute or fetch operation.
The .NET Framework Data Provider for Oracle does not support the question mark (?) placeholder for passing parameters to an SQL statement called by an OracleCommand of CommandType.Text. In this case, named parameters must be used. For example:
SELECT * FROM Customers WHERE CustomerID = :pCustomerID
When using named parameters in an SQL statement called by an OracleCommand of CommandType.Text, you must precede the parameter name with a colon (:). However, in a stored procedure, or when referring to a named parameter elsewhere in your code (for example, when adding OracleParameter objects to the Parameters property), do not precede the named parameter with a colon (:). The .NET Framework Data Provider for Oracle supplies the colon automatically.
Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.