►► Check out our courses: https://bit.ly/cdmz-courses
►► Support us on Patreon and get the source code: / codemaze
In this video, we are going to learn how to use Dapper in the ASP.NET Core Web API project. We are going to talk about Dapper overall, how to use different queries and executions, how to execute stored procedures, and how to create multiple queries inside a transaction.
0:00 Introduction
2:24 Dapper Installation
10:23 Dapper Queries
16:45 Parameters with Dapper
19:59 Creating New Records with Dapper
28:24 Update and Delete with Dapper
35:23 Stored Procedures with Dapper
41:23 Multiple Queries and Mappings
51:11 Transactions with Dapper
LINKS MENTIONED IN THE VIDEO:
The link to the Global Error Handling video:
►► • Global Error Handling in ASP.NET Core...
For the mentioned videos Handling GET requests:
►► • Handling GET requests with ASP.NET Co...
Handling POST, PUT, and DELETE Requests:
►► • Handling POST, PUT and DELETE Request...
FOLLOW US ON SOCIAL MEDIA!
►► / marinko-spasojevic
►► / codemazeblog
►► / codemazeblog
VIDEO SUMMARY:
Using Dapper with ASP.NET Core Web API
Dapper is a Micro ORM - Object Relational mapper, which we can use to communicate with the database in our projects. By using Dapper, we can write SQL statements as we like to do in the SQL Server.
Dapper has great performance because it doesn’t translate queries that we write in .NET to SQL. It is important to know that Dapper is SQL Injection safe because we can use parameterized queries, and that’s something we should always do. One more important thing is that Dapper supports multiple database providers. It extends ADO.NET’s IDbConnection and provides useful extension methods to query our database. Of course, we have to write queries compatible with our database provider.
When we talk about these extension methods, we have to say that Dapper supports both synchronous and asynchronous method executions. In this video, we are going to use the asynchronous version of those methods.
So, let’s learn more about these extension methods. To do that, let’s visit our article…
We can see that Dapper extends the IDbConnection interface with several methods:
Execute, Query, QueryFirst, QueryFirstOrDefault, QuerySingle, QuerySingleOrDefault, and QueryMultiple.
Also, we can see that all of these methods come with the async functionality: ExecuteAsync, QueryAsync, QueryFirstAsync, and so on.
Of course, you can see from the description what each method does, and by looking at that we can see that some of them are pretty similar to the LINQ methods ( First, FirstOrDefault, Single, SingleOrDefault).
Информация по комментариям в разработке