Why nHibernate?

PROBLEM:

You have a solid object model, with relationships between objects that are 1:1, 1:m, and m:n, don't have stored procedures, and likes dynamic SQL

SOLUTION:
Working with object-oriented software and a relational database can be cumbersome and time consuming. Hibernate is an Object/Relational Mapping tool for Java and .NET environments. The term Object/Relational Mapping (ORM) refers to the technique of mapping a data representation from an object model to a relational data model with a SQL-based schema.

Hibernate not only takes care of the mapping from Java/.NET classes to database tables (and from Java/.NET data types to SQL data types), but also provides data query and retrieval facilities. It can also significantly reduce development time otherwise spent with manual data handling in SQL and JDBC/ADO.NET

Hibernate's goal is to relieve the developer from 95 percent of common data persistence related programming tasks.

Hibernate may not be the best solution for data-centric applications that only use stored-procedures to implement the business logic in the database, it is most useful with object-oriented domain models and business logic in the Java/.NET-based middle-tier. However, Hibernate can certainly help you to remove or encapsulate vendor-specific SQL code and will help with the common task of result set translation from a tabular representation to a graph of objects.

Hibernate.org

http://www.hibernate.org

What are the advantages and disadvantages of using an ORM?
http://stackoverflow.com/questions/398134/what-are-the-advantages-of-using-an-orm

ORM Hate?
http://martinfowler.com/bliki/OrmHate.html

If you find this solution useful, you are welcome to press one of the ads in this page.. Thanks!