I am wondering exactly what the best feature(s) from the orm framework you utilize and what features you are using most?

What's the reason you're considering the framework you utilize?

I am just attempting to do a comparison and wondered if any offers advantages within the other. (it's ok searching this but derive top notch user encounters!)

Particularly I am searching for b .Internet framework but nonetheless interested in ORM/features in other langauges.

Thanks ahead of time!

We simply lately experienced the entire process of determining between Entity Framework and NHibernate. Although my primary tendency ended up being to lean towards NHibernate, considering the fact that Microsoft's history of really adhering having a technologies have been under stellar here previously couple of years (ex: Linq To SQL, dead at version 1, or a far more recent example were MS made the decision to ditch ASP.Internet Ajax Library client templates, check this), we still made the decision to choose Entity Framework.

We chose it for an additional reasons:

  1. We're a Microsoft only shop, therefore it integrated well with this existing tool set.
  2. We loved the truth that it had the built-in modeling capacity by using it in Visual Studio 2010.
  3. We loved the capacity of having the ability to reverse engineer a DB schema into an entity data model (it was really awesome).
  4. We loved the truth that everything we needed was virtually available as they are, in contrast to NHibernate where we would need to use different tools to complete visual modeling, the mapping files could be a discomfort to cope with sometimes) also it did not integrate as nicely with Visual Studio.

Whether choosing Entity Framework was the best choice remains to appear. Almost always there is the opportunity that Microsoft could pull another "Linq To SQL" and say, "Hey, we are throwing out Entity Framework, sorry about this, you ought to have gone with NHibernate". But we made the decision that as it is on 2. with Versus 2010, there's a minimum of a strong possibility that it will likely be around for any couple of years.

So despite the fact that we loved NHibernate's proven history a lot better than Entity Framework's, we opted for Entity Framework for that reasons I pointed out above.

I believe you just need to consider the benefits and drawbacks of every tool, examine all of the options, and then try to get the best decision you are able to.

I personally use empire-db by Apache.

The primary reason is the fact that I eliminate XML or annotations for determining database schemes. I truly hate shifting complexity from coding to setting up needing to deal with billions of xml configuration files and - a whole lot worse - distributed configuration using annotations.

I am wondering exactly what the best feature(s) from the orm framework you utilize and what features you are using most?

I authored my very own ORM. Features include:

  • Machine-produced code for every table, according to abstract table definitions

  • A library/framework, which functions up for grabs definitions and also the run-time data, to be able to implement ueful functions like:

    • Create tables (or update table definitions)
    • CRUD
    • Triggered saved methods which create history records whenever a table's contents are transformed
    • Support for tree-like data (using nested sets)
    • Changing application types (C# class instances) to SQL data records and the other way around

What's the reason you're considering the framework you utilize?

I did not desire to use a current ORM, because I feared which i might eventually discover that it did't implement some feature which i wanted, which I'd then find it hard to include that feature.

I needed to make use of an ORM, because I did not wish to write and keep code for everybody table.

I authored Object Data Blocks to give the following outstanding features

  • Uses .internet classes to explain the db schema - no mapping files
  • Produces saved procs for those db access
  • Both classes and queries support inheritance
  • Automated deployment or sql script generation for DBA's

Its best summarized as an item persistence style ORM.