Better Entities with Nullable Types

Friday May 4th 2007 by DatabaseJournal.com Staff

Tired of checking database entries for null values? Learn how you can use Nullable types to make fields and properties accept nulls.

[From Developer.com]

There is an impedance mismatch between objects and normalized relational databases. Everyone knows this. Almost everyone has tried to fix it—think object-oriented databases—and some people have gotten famous off of proposed solutions. (Deservedly so or not.) Well, truth be told Microsoft is working on an ADO.NET Entity Framework to address this issue. The issue phrased using my words is getting data from databases into objects makes for better programming but is time consuming, tedious, and not altogether convenient. From what I know of LINQ, LINQ for Data, and the Entity Framework, they may really be on to something.

The article continues at http://www.developer.com/db/article.php/3673991

Mobile Site | Full Site