ZZZ Projects

I don't like SQLBulkCopy. So much code to write, especially when you need to insert related entities. And it's error-prone. And it doesn't work on other databases. I prefer cross-database libraries for bulk writes for EF Core, such as Entity Framework Extensions.

With Dapper you run the application and it crashes because of a bug in SQL string Here is how to fix it 👇 Dapper is fast and gives you full control over SQL. But that control comes with a hidden cost. Every INSERT, UPDATE, and DELETE you write lives inside a string. And strings have zero type safety. ↳ Rename a column? No compile error. ↳ Change a property type? No compile error. ↳ Misspell a parameter name? No compile error. You only find out something is broken when your app crashes at runtime. Here is what most developers do when using Dapper: ❌ Write SQL commands as plain strings ❌ Map every parameter by hand ❌ Repeat the same column lists across Insert, Update, and Delete ❌ Hardcode table and schema names everywhere One small refactor breaks half of your queries. And the compiler will not save you. There is a much better way. In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗠𝗮𝗽𝗽𝗶𝗻𝗴. Dapper Plus gives you 3 ways to map your entities to the database - all type-safe. 𝟭. 𝗔𝘂𝘁𝗼 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 → Zero configuration needed → Library matches class name to table name → Properties match column names automatically → Just call SingleInsert or BulkInsert and it works 𝟮. 𝗗𝗮𝘁𝗮 𝗔𝗻𝗻𝗼𝘁𝗮𝘁𝗶𝗼𝗻𝘀 → Use [Table], [Column], [Key], [NotMapped] attributes → Familiar to anyone using EF Core → Keeps mapping next to your model 𝟯. 𝗙𝗹𝘂𝗲𝗻𝘁 𝗔𝗣𝗜 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 → Full control with strongly-typed lambdas → Map only what you need: .Map(x => new { x.Name, x.Price }) → MapAuto method and DapperPlus figures it out for you → Refactor-friendly: rename a property and the compiler tells you You can also organize mappings with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗖𝗼𝗻𝘁𝗲𝘅𝘁: → Global context - configure once at startup → Instance context - configure per use case → Inheritance context - reuse mappings across services And the best part? The same mapping works for 𝗯𝗼𝘁𝗵 free Single methods 𝗮𝗻𝗱 paid Bulk methods. No more SQL strings scattered across your codebase. No more runtime surprises after a refactor. Just clean, type-safe writes. Watch the full video and see all 3 mapping approaches in action. P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed. Get started with Dapper Plus Mapping: dapper-plus.net/mapping?utm_… Here is the source code: github.com/anton-martyniuk/e… How do you solve runtime bugs in SQL strings when using Dapper? Share below 👇 —— ♻️ Repost to help others write type-safe Dapper queries ➕ Follow me ( @anton-martyniuk ) to improve your .NET and Architecture Skills Many thanks to @zzzprojects for sponsoring this post

📌 Important note: You can use the following methods for free in Dapper Plus: → SingleInsert - insert one entity without writing SQL → SingleUpdate - update one entity → SingleDelete - delete one entity → SingleMerge - upsert in one line (insert or update) → SingleSynchronize - keep your data in sync with the source → CreateTable - create the table directly from your C# class Get started with Dapper Plus: dapper-plus.net/?utm_source=…

Dapper 𝗵𝗮𝘀 𝗮 𝗯𝗶𝗴 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗽𝗲𝗻𝗮𝗹𝘁𝘆 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 insert multiple rows. Here is how to address this problem 👇 Developers love Dapper for blazing-fast reads. But for inserting or updating many rows, it becomes painfully slow (even slower than EF Core). But Why? Dapper sends each row to the database one by one. 10,000 rows = 10,000 round-trips. And here is another problem: ↳ You need to write a lot of boilerplate code when using Dapper. Here is what most developers do when using Dapper: ❌ Write manual INSERT and UPDATE SQL statements ❌ Build complex SQL with hundreds of parameters by hand ❌ Write CREATE TABLE scripts And the problem is that you don't have type safety when writing SQL commands inside strings. When something goes wrong you will only know at runtime. There is a much better way. In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀. 👉 𝗦𝘁𝗼𝗽 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗖𝗼𝗺𝗽𝗹𝗲𝘅 𝗦𝗤𝗟 𝘁𝗼 𝗦𝗮𝘃𝗲 𝗗𝗮𝘁𝗮 - 𝗟𝗲𝘁 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗗𝗼 𝗜𝘁 𝗳𝗼𝗿 𝗬𝗼𝘂. Dapper Plus gives you clean, simple methods for every write operation. 𝗙𝗿𝗲𝗲 𝗦𝗶𝗻𝗴𝗹𝗲 𝗠𝗲𝘁𝗵𝗼𝗱𝘀: → SingleInsert - insert one entity without writing SQL → SingleUpdate - update one entity → SingleDelete - delete one entity → SingleMerge - upsert in one line (insert or update) → SingleSynchronize - keep your data in sync with the source → CreateTable - create the table directly from your C# class No more manual SQL. No more parameter mapping by hand. Just call the method and Dapper Plus handles the rest. All single methods are 𝗳𝗿𝗲𝗲 𝘁𝗼 𝘂𝘀𝗲. 𝗣𝗮𝗶𝗱 𝗕𝘂𝗹𝗸 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 (for high performance): → BulkInsert → BulkUpdate → BulkDelete → BulkMerge → BulkSynchronize This is where the real magic happens. I inserted 10,000 product records into the database: ❌ Dapper: 7,000 ms ✅ Dapper Plus BulkInsert: 300 ms That is over 𝟵𝟲% 𝗳𝗮𝘀𝘁𝗲𝗿 with a single line of code. Dapper Plus supports SQL Server, PostgreSQL, MySQL, Oracle, MariaDB, and SQLite. Watch the full video and see every method in action. P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed. Get started with Dapper Plus: dapper-plus.net?utm_source=a… Here is the source code: github.com/anton-martyniuk/e… How do you currently handle bulk inserts in Dapper? Share below 👇 —— ♻️ Repost to help others speed up their Dapper write queries ➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills Many thanks to @zzzprojects for sponsoring this post