OdbcCommandBuilder.GetInsertCommand 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.
Gets the automatically generated OdbcCommand object required to perform insertions at the data source.
Overloads
| GetInsertCommand() |
Gets the automatically generated OdbcCommand object required to perform insertions at the data source. |
| GetInsertCommand(Boolean) |
Gets the automatically generated OdbcCommand object required to perform insertions at the data source. |
Remarks
You can use the GetInsertCommand method for informational or troubleshooting purposes because it returns the OdbcCommand object to be executed.
You can also use GetInsertCommand as the basis of a modified command. For example, you might call GetInsertCommand 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 GetInsertCommand 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 GetInsertCommand.
GetInsertCommand()
- Source:
- OdbcCommandBuilder.cs
- Source:
- OdbcCommandBuilder.cs
Gets the automatically generated OdbcCommand object required to perform insertions at the data source.
public:
System::Data::Odbc::OdbcCommand ^ GetInsertCommand();public System.Data.Odbc.OdbcCommand GetInsertCommand ();override this.GetInsertCommand : unit -> System.Data.Odbc.OdbcCommandmember this.GetInsertCommand : unit -> System.Data.Odbc.OdbcCommandPublic Function GetInsertCommand () As OdbcCommandReturns
The automatically generated OdbcCommand object required to perform insertions.
Remarks
You can use the GetInsertCommand method for informational or troubleshooting purposes because it returns the OdbcCommand object to be executed.
You can also use GetInsertCommand as the basis of a modified command. For example, you might call GetInsertCommand 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 GetInsertCommand 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 GetInsertCommand.
See also
Applies to
GetInsertCommand(Boolean)
- Source:
- OdbcCommandBuilder.cs
- Source:
- OdbcCommandBuilder.cs
Gets the automatically generated OdbcCommand object required to perform insertions at the data source.
public:
System::Data::Odbc::OdbcCommand ^ GetInsertCommand(bool useColumnsForParameterNames);public System.Data.Odbc.OdbcCommand GetInsertCommand (bool useColumnsForParameterNames);override this.GetInsertCommand : bool -> System.Data.Odbc.OdbcCommandPublic Function GetInsertCommand (useColumnsForParameterNames As Boolean) As OdbcCommandParameters
- useColumnsForParameterNames
- Boolean
If true, generate parameter names matching column names, if it is possible. If false, generate @p1, @p2, and so on.
Returns
The automatically generated OdbcCommand object required to perform insertions.
Remarks
You can use the GetInsertCommand method for informational or troubleshooting purposes because it returns the OdbcCommand object to be executed.
You can also use GetInsertCommand as the basis of a modified command. For example, you might call GetInsertCommand 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 GetInsertCommand 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 GetInsertCommand.
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 DbCommandBuilder to generate parameters based on the column names instead. This succeeds only if the following conditions are met:
The ParameterNameMaxLength has been specified, and its length is equal to or greater than the generated parameter name.
The generated parameter name meets the criteria specified in the ParameterNamePattern regular expression.
A ParameterMarkerFormat is specified.
