Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why not look at <a href="http://subsonicproject.com/" rel="nofollow noreferrer">subsonic</a>? I like it over the others because it's lightweight maps transparently to the database scheme (uses ActiveRecord) and fulfills all your requirements.</p> <blockquote> <p>It has to be very productive.</p> </blockquote> <p>I think this is the job of every ORM? With subsonic you can use the Controller (for databinding) or just execute the Save method on any ORM object.</p> <blockquote> <p>It should allows me to extend the objects</p> </blockquote> <p>Extending the generated classes is easy, they are all defined as partials. And you can even edit the templates. (They are T4 templates you include in your project, so you have complete control over how and what is generated)</p> <blockquote> <p>It has to be (at least allmost) database agnostic</p> </blockquote> <p>I think this is kinda basic for any ORM. Subsonic supports a lot of database of which the well knowns are: Oracle, mySql, MsSql, SqlLite, SqlCE. You can look at the database support list <a href="http://subsonicproject.com/docs/Supported_Databases" rel="nofollow noreferrer">here</a>.</p> <blockquote> <p>It has to have not so much configuration or must be based on conventions</p> </blockquote> <p>Yes, it is absolutely convention over configuraion or opinionated as they call it. For a summary of the conventions look <a href="http://subsonicproject.com/docs/Conventions" rel="nofollow noreferrer">here</a>.</p> <blockquote> <p>It should allows me to work with Linq</p> </blockquote> <p>Absolutely, since version 3.0 Linq is supported.</p> <p>For a comparisson between nhibernate, LinqToSql and subsonic read <a href="http://subsonicproject.com/docs/Comparisons" rel="nofollow noreferrer">this</a> It's actually a fair and up to date comparison and explicitly outlines the differences in the visions of the different ORM's.</p> <p>Things I miss in subsonic:</p> <ul> <li><p>UnitOfWork support (you could solve this by using the support for transactions.)</p></li> <li><p>IdentityMap support (your objects get cached in some scope (appdomain, threat, web request context, page lifetime, ...) Although you good argue if this is supposed to be part of the ORM, or of some caching layer.</p></li> </ul> <p>I heard hibernate supported both.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload