Although this post is for Entity Framework not Entity Framework Core, It might be useful for someone who wants to achieve the same thing using Entity Framework Core (I am using V1.1.2). I don’t need navigation properties (although they’re nice) because I am practicing DDD and I want Parent and Child to be two separate … Read more
You can use Data Annotation attributes and Fluent API at the same time. Entity Framework gives precedence to Fluent API over Data Annotations attributes.
The problem is that you create more contexts. First you create the clubs. It’s ok. But when you create the persons, you fetch the clubs via GetClubs, but for each club you dispose the actual entity framework context so you end up with detached entities. At InsertPersons you add detached club entities to the new … Read more
I found the answer. Of course, it is possible to convert DbSet in Entity framework to ObjectQuery using the below lines of code. ObjectContext objectContext = ((IObjectContextAdapter)db).ObjectContext; ObjectSet<Request> objectSet = objectContext.CreateObjectSet<Request>(“Requests”); where, db – Context class inherting from DbContext. Requests – DbSet<Request> defined in Context class. objectSet – Can now be passed as ObjectQuery.
That is because your _database is derived from DbContext and your AccountsOfMonth is DbSet<>. In such case you cannot use ObjectQuery directly because DbSet<> produces DbQuery<> which is not convertible to ObjectQuery<>. You must either use DbQuery<> directly: var result = from acm in this._database.AccountsOnMonth where ((acm.Year == year) && (acm.Month == month)) select acm.Id; … Read more
While doing some research about Entity Framework I came across the following post: http://romiller.com/2011/05/23/ef-4-1-multi-tenant-with-code-first/ It doesn’t quite give me a single dbContext to work with but it does only use a single connection (which was my reasoning behind not wanting to use multiple dbContexts). After setting up the following code: public class oraDbContext : DbContext … Read more
From Entity Framework Code First book (page 155): The SQLQuery method always attempts the column-to-property matching based on property name… None that the column-to-property name matching does not take any mapping into account. For example, if you had mapped the DestinationId property to a column called Id in the Destination table, the SqlQuery method would … Read more
Solution with a command interceptor It is definitely possible, though it’s a bit of a hack. You can alter the CREATE DATABASE command with a command interceptor. Il will intercept all the commands sent to the database, recognize the database creation command based on a regex expression, and alter the command text with your collation. … Read more
Try this: var context = new YourDbContext(); var adapter = (IObjectContextAdapter)context; var objectContext = adapter.ObjectContext;
Unfortunately, enums are not natively supported on EF 4.1. Here’s one rather known article on how to deal with them: Faking enums on EF 4. It does, however, require a wrapper. There’s a simpler way to map enums in EF 4 however: just create an int property on your class to represent the int value … Read more