Databases
StackOverflow2013
Postsdbo
POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
    primarykey
    data
    text
    <p>The problem:</p> <ol> <li>A DBA-controlled database with a Stored Procedure-only mandate.</li> <li>An expectation that the domain be defined in POCO's.</li> </ol> <p>So I decided that I need an ORM designed for stored procedures and/or legacy databases.</p> <p>Ideally the ORM should allow me to declaratively (or fluently) map domain objects to CRUD stored procedures.</p> <p>Some findings thus far:</p> <ol> <li><b>NHibernate</b> would work if only I could control the queries that are generated for lazy-loading.</li> <li><b>iBATIS.NET</b> would work perfectly, but I can't find any examples of: <ol> <li>object state tracking (new/updated/deleted/etc)</li> <li>parent/child commit transactions (if a parent is updated, update all dirty child objects as well).</li> </ol></li> <li>An <b>In-House</b> developed ORM that works with our database conventions is an option and we have already started with this. But I want to make sure we don't have any other choice.</li> </ol> <p>Non-Options:</p> <ol> <li><b>SubSonic</b> does wrap stored procs, but it doesn't <i>map</i> between procs and entities. I could implement a mapper of some sort if it came to it, but there are other factors also weighting against SubSonic, such as lacking VS2005 (or SharpDevelop) support and mingling data-access with domain objects.</li> <li><b>Dropping the SProcs</b> is not an option. Data integrity is a HUGE concern for the DBA's and the higher-ups and they feel safest with SProcs. It's not my place to convince them otherwise.</li> </ol> <p>Does anyone know of an ORM that suits my needs, <b>or a way to overcome the limitations in an ORM that doesn't suit my needs 100%</b>?</p> <p><i>Any</i> suggestions welcome!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. USMichael Maddox
      1. VTFavorite
    3. VO
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. This table or related slice is empty.
      1. VTDownMod
    1. COI'm not sure if "dirty tracking" or "cascading updates" are good descriptive terms of the features I'm talking about... I've never had to communicate this problem so I have no idea what the correct terminology is.
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. This table or related slice is empty.
    2. COPersonally, I would drop the dba and let him do something more useful than writing sprocs
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. USPaco
    3. COI wouldn't go so far as to enforcing a stored-proc-only rule, but to be fair: I see benefits in mapping domain objects to queries instead of tables. So even if we did get rid of the stored procs I'd still like to know what my options are.
      singulars
      1. POIs there a Query-Mapper like iBATIS.NET but with dirty tracking, lazy-loading and cascading updates?
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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