Contents tagged with Entity Framework Core
-
Using MongoDB with Entity Framework Core Session
Yesterday I did a talk on a joint Porto.DATA and Azure & AI User Group Portugal event (thanks, Ivan Campos and Pedro Sousa, for inviting me!) on using MongoDB with EF Core. The slides are here (Portuguese only, sorry!).
-
EF Core Entity Validation
Note: I wrote a post about Data Annotations validation here.
-
Soft Deletes with Entity Framework Core – Wrap Up
Those that follow this blog probably know about my series of posts on soft-deletes with EF Core, which you can find here:
-
Soft Deletes with Entity Framework Core – Bulk Deletes
This is post 4 on a series of posts on soft deletes with EF Core. On none of my posts on this series did I mention that these solutions do not work with bulk deletes, introduced in EF Core 7, but they really don't. That is because they rely on the change tracking mechanism and the bulk delete and bulk update functionality does not use it. But as with most of EF Core, there is certainly a way around it, and in this post I will present one, using IQueryExpressionInterceptor, one of the new interceptors introduced in EF Core 7. There is also an open ticket for adding an interceptor mechanism for bulk updates, which will probably also include bulk deletes.
-
Read-Only Entities in EF Core
One feature that has been conspicuously missing from EF Core is read-only entities, meaning, the possibility to mark an entity type as read-only, in which case, no changes to its instances (inserts, updates, deletes) will be allowed; data needs to be added to the database by other means. There is currently an open ticket to track this functionality, which has been open for quite some time. While it is currently not possible to achieve exactly this functionality, there are some possible workarounds that require very little coding.
-
Current Limitations of Entity Framework Core 8
Update: updated on 31/07/2024 for EF Core 8
-
Changing Schema Dynamically in EF Core
Sometimes it may be necessary to change the schema for some entities based upon some criteria. This may be because of multitenancy or because you want to test something and don’t want to pollute the main schema. Here is a possible solution, going directly to the annotations that EF Core uses.
-
ASP.NET Core OData Part 1
Update: see the second post here.
-
Accessing the HttpContext from a DbContext
Sometimes it might be necessary to access the current HttpContext from inside a DbContext, namely, from inside the OnConfiguring or OnModelCreating methods. Why? Well, for once, because of multitenancy: we may want to be able to decide the connection string to use based on the requesting or the host's domain, the current user or some other request parameter. Here the internal dependency injection (Instance) can’t help, because it cannot be used inside these methods.
-
Succinctly Series Readers Awards
