Asp.net core api filtering, sorting, pagination with stored procedures and dapper

dotnet core web api filtering with stored procedure and dapper
dotnet core web api sorting with stored procedure and dapper
dotnet core web api pagination with stored procedure and dapper
filtering in .net core api
sorting in .net core api
pagination in .net core api
filtering records in sql server
sorting records in sql server
pagination in sql server
📎Source code: github.com/rd003/BookHundred (full project)
🎋 Branch for this project: books
.......................................................................................
connect with me:
👉 RUclips: / @ravindradevrani
👉 Twitter: / ravi_devrani
👉 GitHub: github.com/rd003
👉 Medium.com: / ravindradevrani
..........................................
Support my work:
You can buy me a coffee 🍵 : www.buymeacoffee.com/ravindra...
#aspnetcore #dotnet7api

[@qusaialghawi3437]

thanks soo much

[@mahmoudalaa46]

It is better to use EF or Dapper in performance.

[@ravindradevrani]

Dapper
Because it is much closer to ado.net

[@Yourure23626]

I want to use store procedure for same functionality😅 using ef core?

[@ravindradevrani]

😆 ...
But that won't be much problematic, you have sp(logic is there)...just connect it with with ef core's raw query.

[@ravindradevrani]

Dapper is much easier to work with multiple results..

[@Yourure23626]

@@ravindradevrani but i have started with ef core is it possible to use both orm

[@ravindradevrani]

@@Yourure23626 yes it is possible. Thats why they have created it. Its was the words of dapper's creator.
I personally haven't used both of them in a single project. You need to try it out.

[@ravindradevrani]

@@Yourure23626 do not use dapper just for the sake of one stored procedure. You can use sp with ef core also.