Book Image

NHibernate 2 Beginner's Guide

By : Aaron Cure
Book Image

NHibernate 2 Beginner's Guide

By: Aaron Cure

Overview of this book

<p>NHibernate is an open source object-relational mapper, or simply put, a way to retrieve data from your database into standard .NET objects. Quite often we spend hours designing the database, only to go back and re-design a mechanism to access that data and then optimize that mechanism. This book will save you time on your project, providing all the information along with concrete examples about the use and optimization of NHibernate.<br /><br />This book is an approachable, detailed introduction to the NHibernate object-relational mapper and how to integrate it with your .NET projects. If you're tired of writing stored procedures or maintaining inline SQL, this is the book for you.<br /><br />Connecting to a database to retrieve data is a major part of nearly every project, from websites to desktop applications to distributed applications. Using the techniques presented in this book, you can access data in your own database with little or no code.<br /><br />This book covers the use of NHibernate from a first glance at retrieving data and developing access layers to more advanced topics such as optimization and Security and Membership providers. It will show you how to connect to multiple databases and speed up your web applications using strong caching tools. We also discuss the use of third-party tools for code generation and other tricks to make your development smoother, quicker, and more effective.</p>
Table of Contents (19 chapters)
NHibernate 2
Credits
About the Author
About the Reviewers
Preface
Index

Using Data Access Objects


When we originally created our Session object and wrote a couple of queries in Chapter 5, The Session Procession, we created all of our code inline. While this works for a simple sample, in a real application we don't want to embed this logic with our application logic, for a number of reasons.

Embedding our data access logic inside our application presents a few issues. Firstly, if we have our queries in the application, we can't reuse them in other applications without copying them. Second, by decoupling our presentation layer from our data layer, we can take advantage of technologies such as Silverlight and WPF more readily by using web services. Additionally, if we make any changes to our data layer, we would have to go back several places and change it in each place, instead of just fixing it in the data layer.