- Notifications
You must be signed in to change notification settings - Fork2
A simple unit of work implementation on top of Dapper, with some basic CQS in mind
License
giangcoi48k/Dapper.CQS
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
A simple unit of work implementation on top of Dapper, with some basic CQS in mind.
I've found an awesome project,https://github.com/outmatic/Dapper.UnitOfWork, and I decided to extend some features so that the library can be used more easily. That's why I created this project.
For the query, I have already implemented 3 data types: single, list, paged. You just need to create a Query class, which inherits from 3 respective base classes:QueryBase<T>
,QueryListBase<T>
,QueryPagedBase<T>
.
The following example is a pagination query
publicclassPropertyPagedFilterQuery:QueryPagedBase<Property>{[Parameter]publicstring?Name{get;set;}protectedoverrideCommandTypeCommandType=>CommandType.Text;protectedoverridestringProcedure=>@"SELECT *, COUNT(*) OVER() [COUNT]FROM Properties WHERE Name = @Name OR @Name IS NULLORDER BY [Name]OFFSET (@page -1 ) * @pageSize ROWSFETCH NEXT @pageSize ROWS ONLY";publicPropertyPagedFilterQuery(string?name,intpage,intpageSize){Name=name;Page=page;PageSize=pageSize;}}
The default CommandType is StoredProcedure, which means you will specify the Procedure property as Stored Procedure in the database.
Take a look at specific examples in the Example project.
Install-Package Dapper.CQS
dotnet add package Dapper.CQS