插入一个实体(如果它不存在)
Inserting an entity if it doesn't already exist
我们一直在使用 Dapper
和 Dapper.Contrib
以方便我们执行常规数据库操作,这非常好。但是,自从引入 Polly
为我们的某些操作添加重试策略后,我一直无法找到保持相同简单性的方法,因为在执行重试之前需要检查记录是否存在。
这是我们当前如何执行插入的简化示例:
public async Task Insert(Payment payment)
{
var retryPolicy = // Create using Polly.
using (var connection = new SqlConnection(_connectionString))
{
var dao = MapToDao(payment);
await retryPolicy.ExecuteAsync(() => connection.InsertAsync(dao));
}
}
[Table("Payment")]
public class PaymentDao
{
[ExplicitKey]
public Guid PaymentId { get; set; }
// A whole bunch of properties omitted for brevity
}
其中 Payment
是我们的域模型,PaymentDao
是我们的数据访问对象。
我们在调用 Insert
的服务中确实有明确检查重复项的逻辑,但这被重试策略否定了。这意味着自引入 Polly
以来,我们发现插入了少量重复付款。
我可以通过执行以下操作来解决此问题:
public async Task Insert(Payment payment)
{
var retryPolicy = // Create using Polly.
using (var connection = new SqlConnection(_connectionString))
{
var dao = MapToDao(payment);
await retryPolicy.ExecuteAsync(() => connection.ExecuteAsync(
@"IF ((SELECT COUNT(*) FROM dbo.Payment WHERE SubscriptionId = @subscriptionId) = 0)
BEGIN
INSERT INTO Payment
(
PaymentId,
SubscriptionId,
// Lots of columns omitted for brevity.
)
VALUES
(
@PaymentId,
@SubscriptionId,
// Lots of values omitted for brevity.
)
END",
new
{
dao.PaymentId,
dao.SubscriptionId,
// Lots of properties omitted for brevity.
}));
}
}
但是,如您所见,它变得非常冗长。有更简单的方法吗?
您可以考虑先使用模型检查然后执行插入的替代方法,因为搜索使用的参数较少
using (var connection = new SqlConnection(_connectionString)) {
var dao = MapToDao(payment);
var sql = "SELECT COUNT(1) FROM dbo.Payment WHERE SubscriptionId = @subscriptionId";
await retryPolicy.ExecuteAsync(async () => {
var exists = await connection.ExecuteScalarAsync<bool>(sql, new {dao.SubscriptionId});
if(!exists) {
await connection.InsertAsync(dao);
}
});
}
我们一直在使用 Dapper
和 Dapper.Contrib
以方便我们执行常规数据库操作,这非常好。但是,自从引入 Polly
为我们的某些操作添加重试策略后,我一直无法找到保持相同简单性的方法,因为在执行重试之前需要检查记录是否存在。
这是我们当前如何执行插入的简化示例:
public async Task Insert(Payment payment)
{
var retryPolicy = // Create using Polly.
using (var connection = new SqlConnection(_connectionString))
{
var dao = MapToDao(payment);
await retryPolicy.ExecuteAsync(() => connection.InsertAsync(dao));
}
}
[Table("Payment")]
public class PaymentDao
{
[ExplicitKey]
public Guid PaymentId { get; set; }
// A whole bunch of properties omitted for brevity
}
其中 Payment
是我们的域模型,PaymentDao
是我们的数据访问对象。
我们在调用 Insert
的服务中确实有明确检查重复项的逻辑,但这被重试策略否定了。这意味着自引入 Polly
以来,我们发现插入了少量重复付款。
我可以通过执行以下操作来解决此问题:
public async Task Insert(Payment payment)
{
var retryPolicy = // Create using Polly.
using (var connection = new SqlConnection(_connectionString))
{
var dao = MapToDao(payment);
await retryPolicy.ExecuteAsync(() => connection.ExecuteAsync(
@"IF ((SELECT COUNT(*) FROM dbo.Payment WHERE SubscriptionId = @subscriptionId) = 0)
BEGIN
INSERT INTO Payment
(
PaymentId,
SubscriptionId,
// Lots of columns omitted for brevity.
)
VALUES
(
@PaymentId,
@SubscriptionId,
// Lots of values omitted for brevity.
)
END",
new
{
dao.PaymentId,
dao.SubscriptionId,
// Lots of properties omitted for brevity.
}));
}
}
但是,如您所见,它变得非常冗长。有更简单的方法吗?
您可以考虑先使用模型检查然后执行插入的替代方法,因为搜索使用的参数较少
using (var connection = new SqlConnection(_connectionString)) {
var dao = MapToDao(payment);
var sql = "SELECT COUNT(1) FROM dbo.Payment WHERE SubscriptionId = @subscriptionId";
await retryPolicy.ExecuteAsync(async () => {
var exists = await connection.ExecuteScalarAsync<bool>(sql, new {dao.SubscriptionId});
if(!exists) {
await connection.InsertAsync(dao);
}
});
}