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

Laying the foundation—table layouts


One of the most important things you can do from the beginning is to lay out your tables and entire data structure logically. Spending a few extra minutes in the beginning when designing a logical database can save you hours or even days worth of work later on. You would be surprised at the amount of time it takes to "work around" a bad database design, or worse, having to go back and "re-plumb" your data objects to make them work correctly.

The two rules I like to follow when creating a database are:

  • Lay out objects in the database so that they are organized logically, either by the data they store or the business logic they represent

  • Don't store duplicate data

For example, if we were trying to model an ordering system, we would need to store information about the order, the related customer, the products they ordered, their billing and shipping address, and so on. It would be simple enough to create a single table to store all of this data, but that would...