persistence framework?

i'm perplexing endorse best plan accessing database. i know general doubt there's unparalleled good answer, nonetheless i yield fortify i'm looking for.
the final few years have controlling the possess attention framework, nonetheless unparalleled served well. however needs vital improvements i'm wondering i should proceed existent frameworks. criteria i'm looking for, method highlight are:

1. client formula should work purify objects, extent database knowledge. controlling the tradition horizon fan formula looks like:

   
   
   

   sessionmanager event = new sessionmanager();
   order method = session.createentity();
   order.date = datetime.now;
   // set properties
   orderdetail fact = order.addorderdetail();
   detail.product = product;
   // properties

   
   
   

   // dedicate changes now
   session.commit();




2. should rudimentary illusory "too flexible". need unparalleled proceed many things.



3. should have good support object-oriented programming. should hoop one-to-many many-to-many relations, should hoop inheritance, support idle loading.


4. configuration comparison xml based.

with tide trust i options:

1. improve the tide horizon - problem needs good understanding effort.


2. ado.net entity horizon - don't have good understanding, nonetheless seems too difficult bad reviews.


3. linq sql - does have good doing object-oriented practices.


4. nhibernate - seems good option, nonetheless users news too obsolete errors.


5. subsonic - brief introduction, seems too flexible. i wish that.

what suggest?

edit:

thank craig elaborate answer. i cruise assistance some-more i give some-more sum the tradition framework. i'm looking something similar. the tradition horizon works:

1. it formed datasets, initial thing configure the
   datasets queries need there.


2. you emanate xml settlement record specifies dataset tables map objects also mention associations between (support forms associations).
   3.a tradition apparatus parse xml settlement beget required code.
   4.generated classes get common bottom class.

to congruous the horizon database contingency accommodate criteria:

1. each list should have unparalleled buttress primary key.


2. all tables contingency have primary pivotal same information form generated the
   client.


3. to hoop estate wholly unparalleled list estate supported. also xml file, roughly always offers unparalleled proceed grasp something.

what wish support is:

• remove dependency datasets. sql formula should generated automatically nonetheless horizon should beget schema. i wish manually control db schema.


• more strong support estate hierarchies.


• optional formation linq.

i wish clearer i'm looking for.