SqlCommandBuilder.GetDeleteCommand Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Overloads
| GetDeleteCommand() |
Gets the automatically generated SqlCommand object required to perform deletions on the database. |
| GetDeleteCommand(Boolean) |
Gets the automatically generated SqlCommand object that is required to perform deletions on the database. |
GetDeleteCommand()
- Source:
- SqlCommandBuilder.cs
- Source:
- SqlCommandBuilder.cs
Gets the automatically generated SqlCommand object required to perform deletions on the database.
public:
Microsoft::Data::SqlClient::SqlCommand ^ GetDeleteCommand();public Microsoft.Data.SqlClient.SqlCommand GetDeleteCommand();override this.GetDeleteCommand : unit -> Microsoft.Data.SqlClient.SqlCommandPublic Function GetDeleteCommand () As SqlCommandReturns
The automatically generated SqlCommand object required to perform deletions.
Remarks
An application can use the GetDeleteCommand() method for informational or troubleshooting purposes because it returns the SqlCommand object to be executed.
You can also use GetDeleteCommand() as the basis of a modified command. For example, you might call GetDeleteCommand() and modify the CommandTimeout value, and then explicitly set that on the SqlDataAdapter.
After the SQL statement is first generated, the application must explicitly call RefreshSchema() if it changes the statement in any way. Otherwise, the GetDeleteCommand() will still be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either Update(DataSet) or GetDeleteCommand().
For more information, see Generating Commands with CommandBuilders.
Applies to
GetDeleteCommand(Boolean)
- Source:
- SqlCommandBuilder.cs
- Source:
- SqlCommandBuilder.cs
Gets the automatically generated SqlCommand object that is required to perform deletions on the database.
public:
Microsoft::Data::SqlClient::SqlCommand ^ GetDeleteCommand(bool useColumnsForParameterNames);public Microsoft.Data.SqlClient.SqlCommand GetDeleteCommand(bool useColumnsForParameterNames);override this.GetDeleteCommand : bool -> Microsoft.Data.SqlClient.SqlCommandPublic Function GetDeleteCommand (useColumnsForParameterNames As Boolean) As SqlCommandParameters
- useColumnsForParameterNames
- Boolean
If true, generate parameter names matching column names if possible. If false, generate @p1, @p2, and so on.
Returns
The automatically generated SqlCommand object that is required to perform deletions.
Remarks
An application can use the GetDeleteCommand() method for informational or troubleshooting purposes because it returns the SqlCommand object to be executed.
You can also use GetDeleteCommand() as the basis of a modified command. For example, you might call GetDeleteCommand() and modify the CommandTimeout value, and then explicitly set that on the SqlDataAdapter.
After the SQL statement is first generated, the application must explicitly call RefreshSchema() if it changes the statement in any way. Otherwise, the GetDeleteCommand() will still be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either Update(DataSet) or GetDeleteCommand().
The default behavior, when generating parameter names, is to use @p1, @p2, and so on for the various parameters. Passing true for the useColumnsForParameterNames parameter lets you force the command builder to generate parameters based on the column names instead. This succeeds only if the following conditions are met:
For more information, see Generating Commands with CommandBuilders.