我在问自己是否有可能检查ADO.NET中是否可以回滚当前事务。ADO.NET检查是否可能回滚
在MSDN提出以下建议执行:
private static void ExecuteSqlTransaction(string connectionString)
{
using (SqlConnection connection = new SqlConnection(connectionString))
{
connection.Open();
SqlCommand command = connection.CreateCommand();
SqlTransaction transaction;
// Start a local transaction.
transaction = connection.BeginTransaction("SampleTransaction");
// Must assign both transaction object and connection
// to Command object for a pending local transaction
command.Connection = connection;
command.Transaction = transaction;
try
{
command.CommandText =
"Insert into Region (RegionID, RegionDescription) VALUES (100, 'Description')";
command.ExecuteNonQuery();
command.CommandText =
"Insert into Region (RegionID, RegionDescription) VALUES (101, 'Description')";
command.ExecuteNonQuery();
// Attempt to commit the transaction.
transaction.Commit();
Console.WriteLine("Both records are written to database.");
}
catch (Exception ex)
{
Console.WriteLine("Commit Exception Type: {0}", ex.GetType());
Console.WriteLine(" Message: {0}", ex.Message);
// Attempt to roll back the transaction.
try
{
transaction.Rollback();
}
catch (Exception ex2)
{
// This catch block will handle any errors that may have occurred
// on the server that would cause the rollback to fail, such as
// a closed connection.
Console.WriteLine("Rollback Exception Type: {0}", ex2.GetType());
Console.WriteLine(" Message: {0}", ex2.Message);
}
}
}
}
此外,还有注:回滚当一个事务 的try/catch异常处理应始终使用。如果连接终止或者事务已在服务器上回滚,则回滚会生成InvalidOperationException。
但我不能真正相信try/catch是推荐的解决方案来检查回滚是否可能。
我知道在SQL Server实现中,如果事务是“僵尸”,则SQLTransaction对象在Connection属性上返回null。
但是,这是相当具体的实现,它只适用于SQL Server。
那么,是否有一个数据库独立的方式来检测事务是否可以回滚?
TIA 马丁