ffernandolima / ef-core-data-access Goto Github PK

Example:

...
public void UpdateBlog()
{
    var repository = _unitOfWork.Repository<Blog>();

    var blog = await repository.UpdateAsync(model); ///Not work
    
    _unitOfWork.SaveChangesAsync();
}
...

Look like IAsyncRepository<T> in EntityFrameworkCore.Repository.Interfaces doesn't have method below:

 Task<T> UpdateAsync(
      T entity, 
      params Expression<Func<T, object>>[] properties
      CancellationToken cancellationToken = default (CancellationToken));

Hello.
I really liked your library.

I would like to talk about the outcome. In EF 5 AddPooledDbContextFactory. This allows the pool factory to be used by the context. Is it possible to use it in this library?

Unit of work is a way to encapsulate db context but i see it is fully public. Some might need to access DbContext but thats why i ask to make it protected so people can just create a simple wrapper around your UnitOfWork to use it but currently forcing public DbContext does not make any sense to me. If there is some other reason that i don't know enlighten me.

Have you ever considered adding support for ExecutionStrategy in conjunction with transactions? I recently ran across a situation where I wasn't able to use the normal create Transaction because of conflicts with the application's existing retry strategy. After a lot of trial and error, I finally settled on creating a new execution strategy and executing the transaction off it. They have an extension method available that wraps the try/catch begin/commit/rollback so there wasn't much to a barebones version (although there are several more signatures you could support) - this was my down and dirty (and definitely not fully tested) method on the UnitOfWork:

public async Task ExecuteInTransactionAsync(Func<Task> operation, Func<Task<bool>> verifySucceeded = null)
{
    var strategy = _context.Database.CreateExecutionStrategy();

    await strategy.ExecuteInTransactionAsync(
        async () => await operation(),
        () => verifySucceeded != null ? verifySucceeded() : Task.FromResult(true)
    );
}

and then you just call it as needed like:

await _unitOfWork.ExecuteInTransactionAsync(
  async () =>
  {
       ......
       await whatever.SaveChangesAsync();
       await whatever.SaveChangesAsync();
       await whatever.SaveChangesAsync();
       ....
  });

Just thought I'd mention it while it was on my mind.

Thanks-

when update entity show me below error

The database operation was expected to affect 1 row(s), but actually affected 0 row(s)

update code is

var updatedCourse = _mapper.Map<Model.Course.Course>(request.Course);
var course = repository.Update(updatedCourse);
await unitOfWork.SaveChangesAsync(cancellationToken: cancellationToken);

How do used UpdateAsync for updateing all property?

Hi, I want to ask about SelectMany?

Are there any alternative or implementation for SelectMany?

I want some things like this

var query = _missionRepository
                .MultipleResultQuery()
                .OrderBy(x => x.StartDate)
                .Page(request.Params.PageNumber, request.Params.PageSize);

I've just started trying to implement this library into a project and I'm having trouble getting it to load a one-to-one relationship.

I have a User entity, and I have a Queue entity. There is a single queue/one-to-one for each user, so I have a Queue property on the User entity using the foreign key.

When I attempt to Include the Queue property, unless I have NoTracking set, it isn't populated.

var repository = _unitOfWork.Repository<User>();

var query = repository.SingleResultQuery()
          .AndFilter(u => u.UserId == userId)
          .Include(src => src.Include(u => u.Queue));
          /////.UseQueryTrackingBehavior(QueryTrackingBehavior.NoTracking);

var user = await repository.SingleOrDefaultAsync(query);

user.Queue will be null here...

var query = repository.SingleResultQuery()
          .AndFilter(u => u.UserId == userId)
          .Include(src => src.Include(u => u.Queue));
          .UseQueryTrackingBehavior(QueryTrackingBehavior.NoTracking);

var user = await repository.SingleOrDefaultAsync(query);

user.Queue is correctly loaded here....

What am I doing wrong?

Thanks-