/// <summary>
/// Executes the given DDL/DML command against the database.
///
/// As with any API that accepts SQL it is important to parameterize any user input to protect against a SQL injection attack. You can include parameter place holders in the SQL query string and then supply parameter values as additional arguments. Any parameter values you supply will automatically be converted to a DbParameter.
/// context.Database.ExecuteSqlCommand("UPDATE dbo.Posts SET Rating = 5 WHERE Author = @p0", userSuppliedAuthor);
/// Alternatively, you can also construct a DbParameter and supply it to SqlQuery. This allows you to use named parameters in the SQL query string.
/// context.Database.ExecuteSqlCommand("UPDATE dbo.Posts SET Rating = 5 WHERE Author = @author", new SqlParameter("@author", userSuppliedAuthor));
/// </summary>
/// <param name="transactionalBehavior"> Controls the creation of a transaction for this command. </param>
/// <param name="sql"> The command string. </param>
/// <param name="parameters"> The parameters to apply to the command string. </param>
/// <returns> The result returned by the database after executing the command. </returns>
public int ExecuteSqlCommand(TransactionalBehavior transactionalBehavior, string sql, params object[] parameters)
{
Check.NotEmpty(sql, "sql");
Check.NotNull(parameters, "parameters");
return(_internalContext.ExecuteSqlCommand(transactionalBehavior, sql, parameters));
}
/// <summary>
/// Executes the given DDL/DML command against the database.
/// </summary>
/// <param name="sql"> The command string. </param>
/// <param name="parameters"> The parameters to apply to the command string. </param>
/// <returns> The result returned by the database after executing the command. </returns>
public int ExecuteSqlCommand(string sql, params object[] parameters)
{
Check.NotEmpty(sql, "sql");
Check.NotNull(parameters, "parameters");
return(_internalContext.ExecuteSqlCommand(sql, parameters));
}
