What is the goal of Entity Framework?
-
I thought the purpose of entity framework was to discharge his duty to write queries (whether in SQL or LINQ). I worked on the framework for manipulating entities without worrying about queries. I think this is the case of NHibernate. This is not the case with the Entity Framework.
-
I thought the purpose of entity framework was to discharge his duty to write queries (whether in SQL or LINQ). I worked on the framework for manipulating entities without worrying about queries. I think this is the case of NHibernate. This is not the case with the Entity Framework.
EF is an ORM. That pretty much sums it up.
-
I thought the purpose of entity framework was to discharge his duty to write queries (whether in SQL or LINQ). I worked on the framework for manipulating entities without worrying about queries. I think this is the case of NHibernate. This is not the case with the Entity Framework.
If that is true that you forgot one of two things when using EF 1) you did not call 'SaveChanges()' on your DbContext. or 2) Your EF configuration has the change tracker disabled. There is always the possibility that something is just plain broken - like you are modifying properties which are not mapped.
-
I thought the purpose of entity framework was to discharge his duty to write queries (whether in SQL or LINQ). I worked on the framework for manipulating entities without worrying about queries. I think this is the case of NHibernate. This is not the case with the Entity Framework.
I think the goal of EF (and any ORM) is to abstract away the detail of the data storage implementation. If you are still thinking in terms of tables and SQL then you haven't abstracted enough :-)
-
I think the goal of EF (and any ORM) is to abstract away the detail of the data storage implementation. If you are still thinking in terms of tables and SQL then you haven't abstracted enough :-)
Duncan Edwards Jones wrote:
I think the goal of EF (and any ORM) is to abstract away the detail of the data storage implementation.
SQL is already an abstraction.
Duncan Edwards Jones wrote:
If you are still thinking in terms of tables and SQL then you haven't abstracted enough :)
If you wrote a DAL for your SQL, add this comment on top: redundant leaky abstraction.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Duncan Edwards Jones wrote:
I think the goal of EF (and any ORM) is to abstract away the detail of the data storage implementation.
SQL is already an abstraction.
Duncan Edwards Jones wrote:
If you are still thinking in terms of tables and SQL then you haven't abstracted enough :)
If you wrote a DAL for your SQL, add this comment on top: redundant leaky abstraction.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
But neither are enough of an abstraction if you still know how and where the objects get stored.