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

Why should we use data binding?


Data binding is pretty simple and one of my personal favorite features of ASP.NET. By adding a few simple controls to my page and setting a few properties, my HTML page can become a dynamic, "living" page. I can add data to the database and have it displayed on my page, formatted in any way I want.

Imagine creating a website for your favorite club, and like most clubs, they need a calendar for upcoming events. If you define this in a web page and need to go in every time someone wants to add an event and change the page, how long do you think you would want to be the webmaster?

Wouldn't it be easier on the webmaster if we just create a web page, which is bound to a database table, and allow members to add their own events to the database?