This project is read-only.


Jun 29, 2010 at 12:32 PM

I can't see any way to use nHydrate in any of my applications

It seems designed for database record-editting type applications

But in nearly all my apps there is no symmetry between READs and WRITEs

there is one app - a contact database - that is just a UI for searching and editting db records
that could work with nHydrate
but it uses a custom locking architecture - using optimistic locking
on groups of fields / records that allows some parts of an update to fail
and others to succeed (ie: single update has multiple transactions)
and enforces locking across related groups of fields in a single row

I can't see an easy way to recreate that important behaviour using nHydrate

Furthermore that app is generated dynamically at runtime based on db schema
with overides for any non-default behaviour

That is truly model driven and there is no need for code generation

Also I can setup a new application based on a new database schema in about 30 seconds

Is there something I don't understand about nHydrate?

Jul 1, 2010 at 5:22 AM

Perhaps you have no use for product. Its biggest feature is tying evolutionary database design with a data access layer for business applications. They can evolve in tandem. There are also the other libraries you can create as well like POCO's and IoC layers, but your situation might not fit this.