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

Table layouts


Creating a table layout is a little like art, but don't worry if you're not a "Da Vinci"! If you follow some basic guidelines about table design, you will do just fine.

One of the most important things you can do when you design your tables is give them a good name. The name of the table should describe what types of records and data it is meant to hold. Remember, unless you change it, the name you give your object in the database is the name you will use to refer in the code. Do you really want to create an "S-9619" object every time you create an order, or does creating a "BillOfLading" object make more sense? I think just about every developer in the world would agree that more descriptive names, even if it means a little more typing, make the database structure more understandable and the eventual code more readable in the end.

Table names should be singular, like the objects they represent. Each row of the table in the database will represent a single object such as a "Contact...