Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The main issue I see with this, is that by going with SP you are automatically loosing lot of the flexibility you get when using ORM, specially on the retrieval of information. Because of this, I am sure you won't be able to use All of the features of most ORM.</p> <p>For example, if you use linq2sql, you will have pretty much wrapper to the SPs. You can also map insert, deletes and updates of the generated entities to stored procedures. Where you loose a lot is on the retrieval of information, both because the queries are now fixed (and you might retrieve more information than needed i.e. extra columns - or create lots of SPs) and on lazy loading.</p> <p><strong>Update:</strong> I am more a linq2sql guy, but I would take a second look at the assumptions you are taking about NHibernate. In particular, I doubt it will force column order as it is configured with column names (see <a href="http://nhibernate.info/blog/2008/11/23/populating-entities-from-stored-procedures-with-nhibernate.html" rel="nofollow noreferrer">http://nhibernate.info/blog/2008/11/23/populating-entities-from-stored-procedures-with-nhibernate.html</a>). It also supports something I don't know how to do with linq2sql: <a href="http://nhibernate.info/blog/2008/11/23/populating-entities-with-associations-from-stored-procedures-with-nhibernate.html" rel="nofollow noreferrer">http://nhibernate.info/blog/2008/11/23/populating-entities-with-associations-from-stored-procedures-with-nhibernate.html</a>. Note, I don't mean that last one isn't supported with linq2sql, just that I don't know how to ;)</p>
 

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