Bewerken

Delen via

OdbcCommandBuilder.GetDeleteCommand Method

  • Reference

Definition

Namespace:
System.Data.Odbc
Assembly:
System.Data.Odbc.dll
Assembly:
System.Data.dll
Package:
System.Data.Odbc v9.0.0

Gets the automatically generated OdbcCommand object required to perform deletions at the data source.

Overloads

GetDeleteCommand()

Gets the automatically generated OdbcCommand object required to perform deletions at the data source.
GetDeleteCommand(Boolean)

Gets the automatically generated OdbcCommand object required to perform deletions at the data source.

Remarks

You can use the GetDeleteCommand method for informational or troubleshooting purposes because it returns the OdbcCommand 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 OdbcDataAdapter.

After the SQL statement is first generated, you must explicitly call RefreshSchema if it changes the statement in any way. Otherwise, the GetDeleteCommand still will be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either Update or GetDeleteCommand.

GetDeleteCommand()

Source:
OdbcCommandBuilder.cs
Source:
OdbcCommandBuilder.cs
Source:
OdbcCommandBuilder.cs

Gets the automatically generated OdbcCommand object required to perform deletions at the data source.

public:
 System::Data::Odbc::OdbcCommand ^ GetDeleteCommand();
public System.Data.Odbc.OdbcCommand GetDeleteCommand ();
override this.GetDeleteCommand : unit -> System.Data.Odbc.OdbcCommand
member this.GetDeleteCommand : unit -> System.Data.Odbc.OdbcCommand
Public Function GetDeleteCommand () As OdbcCommand

Returns

OdbcCommand

The automatically generated OdbcCommand object required to perform deletions.

Remarks

You can use the GetDeleteCommand method for informational or troubleshooting purposes because it returns the OdbcCommand 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 OdbcDataAdapter.

After the SQL statement is first generated, you must explicitly call RefreshSchema if it changes the statement in any way. Otherwise, the GetDeleteCommand will be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either Update or GetDeleteCommand.

See also

Applies to

GetDeleteCommand(Boolean)

Source:
OdbcCommandBuilder.cs
Source:
OdbcCommandBuilder.cs
Source:
OdbcCommandBuilder.cs

Gets the automatically generated OdbcCommand object required to perform deletions at the data source.

public:
 System::Data::Odbc::OdbcCommand ^ GetDeleteCommand(bool useColumnsForParameterNames);
public System.Data.Odbc.OdbcCommand GetDeleteCommand (bool useColumnsForParameterNames);
override this.GetDeleteCommand : bool -> System.Data.Odbc.OdbcCommand
Public Function GetDeleteCommand (useColumnsForParameterNames As Boolean) As OdbcCommand

Parameters

useColumnsForParameterNames
Boolean

If true, generate parameter names matching column names, if it is possible. If false, generate @p1, @p2, and so on.

Returns

OdbcCommand

The automatically generated OdbcCommand object required to perform deletions.

Remarks

You can use the GetDeleteCommand method for informational or troubleshooting purposes because it returns the OdbcCommand 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 OdbcDataAdapter.

After the SQL statement is first generated, you must explicitly call RefreshSchema if it changes the statement in any way. Otherwise, the GetDeleteCommand will be using information from the previous statement, which might not be correct. The SQL statements are first generated when the application calls either Update 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 OdbcCommandBuilder to generate parameters based on the column names instead. This succeeds only if the following conditions are met:

See also

Applies to