Click here to Skip to main content
11,790,613 members (62,867 online)
Click here to Skip to main content

Persistent Object Management in Less than 300 Lines of Code

, 8 Oct 2007 CPOL 66.8K 542 70
Rate this:
Please Sign up or sign in to vote.
Presenting a lightweight method to cut out most of the repetitive work of creating data classes.


There's a lot of repetitive work associated with the writing of data classes within the data access layer of an N-tiered architecture. Apart from adding a column to the relevant database table, adding a field to the class involves adding a private variable to hold the field value, a property to expose it to other classes, and several lines to make sure the field is included in insert, fetch, and update operations. If you're using stored procedures (very silly for CRUD queries) there are several more modifications to make. This is dull work, I'm sure you'll agree. Presented here is a lightweight method for taking away all this tedium, such that you only have to add a getter/setter property in order to add a field to a data class.

The technique involves abstracting SQL query writing and execution, and variable storage in data access classes to a base class. In the implementation presented here, I've named this base class "PersistentDataObject". The "less than 300 lines of code" referred to in the title of this post are the lines of code in this base class, the database access class it uses, and a couple of exception classes used as markers to add clarity to exception origins. The complete code is included at the end of the post.


I conceived this idea, before my .NET days, while working on a monolithic PHP project. After writing hundreds of simple CRUD queries that were all basically the same, I realized that it would be a simple matter to abstract all that query writing in such a way that I would never have to write such a simple query again. That was over a year ago. Now I'm a fully paid up ASP.NET developer, and I think the code has reached a level of refinement at which it is ready to be presented to the world. I use the code presented here in every system I build and I love it. Maybe you will too.

Using the Code

Here is a simple Person class created by extending PersistentDataObject:

using System;

public class Person : PersistentDataObject
 public Person() : base("Person", "PersonId") { }
 public Person(int id) : this() { Load(id); }

 public string FirstName
   get { return Get<string>("FirstName"); }
   set { Set("FirstName", value); }
 public string LastName
   get { return Get<string>("LastName"); }
   set { Set("LastName", value); }
 public DateTime DateOfBirth
   get { return Get<DateTime>("DateOfBirth"); }
   set { Set("DateOfBirth", value); }
 public int? LuckyNumber
   get { return Get<int?>("LuckyNumber"); }
   set { Set("LuckyNumber", value); }

Configuring the Data Object Class

The only configuration values necessary for the class are name of the table from which the data is to be retrieved, and the name of the unique id column within that table (assumed to be an integer column). These are passed to PersistentDataObject in the constructor.

public Person() : base("Person", "PersonId") { }

Fetching Data from the Database

The Person class shown above provides a constructor that accepts an integer identifier as an argument. This constructor delegates to the Load method of PersistentDataObject to fetch all data from the database for the row with the specified identifier.

public Person(int id) : this() { Load(id); }

An overload of the Load method is provided that takes a DataRow as an argument. This allows the object to be populated with data from a DataRow that has already been fetched from the database.

Exposing Column Values as Properties

Column Values are exposed by delegating to the Get and Set methods of PersistentDataObject. The Get method takes a string argument indicating the column from which the value should be retrieved. Similarly, the Set method takes a string argument to indicate for which column the value is to be set. This example shows a property exposing a DateTime column:

public DateTime DateOfBirth
get { return Get<DateTime>("DateOfBirth"); }
set { Set("DateOfBirth", value); }

Note that the Get method uses generics to identify the type of the value that should be returned. The type specified should be the appropriate type dependant on the type of the column.

Handling Null Values

Nullable value types come into play in order to handle columns that allow null values. This example shows an integer column for which null values are allowed exposed as a property:

public int? LuckyNumber
get { return Get<int?>("LuckyNumber"); }
set { Set("LuckyNumber", value); }

Note that as string is a reference type, it does not need to be specified as nullable to accept null values.

Inserting, Updating, and Deleting

A Save method is provided that handles both the inserting into, and the updating of objects in the database. If the Save method is called on an object that does not yet exist in the database, then an insertion is performed. If the object does already exist in the database, an update is performed. This code snippet shows an instance of Person being created and a record for it being inserted into the database:

Person person = new Person();
person.FirstName = "Nick";
person.LastName = "Higgs";
person.DateOfBirth = new DateTime(1983, 2, 7);

A Delete method is provided to allow the object to be deleted from the database. This code shows an object for an existing person record being instantiated and then deleted from the database:

Person person = new Person(51);

Closing Remarks

That completes the explanation. I've found that this technique not only takes most of the repetitive work out of writing data objects, but provides a solid foundation to a data access layer, regardless of the complexity of the system.


Modified from an article posted on my (now discontinued) blog


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Nick Higgs
Web Developer
United Kingdom United Kingdom
Since graduating from the University of Sheffield with a Masters degree in Software Engineering in 2005 I have been woking as a professional web developer for a Sheffield new media company.
ASP.Net is currently my primary technology, but I also have substantial experience with PHP and Flex and various Java technologies.

You may also be interested in...

Comments and Discussions

QuestionMultiple object Pin
suraj Chhetry9-Oct-07 20:56
membersuraj Chhetry9-Oct-07 20:56 
AnswerRe: Multiple object Pin
Nick Higgs10-Oct-07 2:25
memberNick Higgs10-Oct-07 2:25 
GeneralInitiative way! Pin
M.Khadem7-Jun-07 4:31
memberM.Khadem7-Jun-07 4:31 
QuestionHow to bind the Person object to a view object Pin
Aliasncnu7-May-07 16:43
memberAliasncnu7-May-07 16:43 
AnswerRe: How to bind the Person object to a view object Pin
Nick Higgs9-May-07 12:12
memberNick Higgs9-May-07 12:12 
GeneralQuestions and suggestions Pin
felipedr19-Apr-07 6:16
memberfelipedr19-Apr-07 6:16 
GeneralRe: Questions and suggestions Pin
Nick Higgs19-Apr-07 13:25
memberNick Higgs19-Apr-07 13:25 
GeneralTransactions Pin
probe5318-Apr-07 23:05
memberprobe5318-Apr-07 23:05 
GeneralRe: Transactions Pin
Nick Higgs19-Apr-07 9:30
memberNick Higgs19-Apr-07 9:30 
GeneralExcellent Article Pin
Dewey9-Apr-07 20:02
memberDewey9-Apr-07 20:02 
GeneralRe: Excellent Article Pin
Nick Higgs10-Apr-07 2:07
memberNick Higgs10-Apr-07 2:07 
General2 security flaws Pin
reinux9-Apr-07 17:21
memberreinux9-Apr-07 17:21 
GeneralRe: 2 security flaws Pin
Nick Higgs10-Apr-07 1:53
memberNick Higgs10-Apr-07 1:53 
GeneralRe: 2 security flaws Pin
Nick Higgs12-Apr-07 11:06
memberNick Higgs12-Apr-07 11:06 
GeneralRe: 2 security flaws Pin
reinux12-Apr-07 14:16
memberreinux12-Apr-07 14:16 
GeneralRe: 2 security flaws Pin
Nick Higgs14-Apr-07 2:20
memberNick Higgs14-Apr-07 2:20 
GeneralRe: 2 security flaws Pin
reinux16-Apr-07 12:06
memberreinux16-Apr-07 12:06 
QuestionStored Procedures "silly" for CRUD operations? Pin
chmod7559-Apr-07 10:10
memberchmod7559-Apr-07 10:10 
AnswerRe: Stored Procedures "silly" for CRUD operations? Pin
Nick Higgs9-Apr-07 13:09
memberNick Higgs9-Apr-07 13:09 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
mr_lasseter9-Apr-07 15:44
membermr_lasseter9-Apr-07 15:44 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
reinux9-Apr-07 17:38
memberreinux9-Apr-07 17:38 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
Nick Higgs10-Apr-07 9:25
memberNick Higgs10-Apr-07 9:25 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
reinux10-Apr-07 10:52
memberreinux10-Apr-07 10:52 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
Nick Higgs10-Apr-07 12:43
memberNick Higgs10-Apr-07 12:43 
GeneralRe: Stored Procedures "silly" for CRUD operations? Pin
reinux11-Apr-07 2:49
memberreinux11-Apr-07 2:49 
Sorry, I didn't mean to be excessively terse but I genuinely don't understand:

1. why you don't see stored procedures being unsuitable for the business tier.
2. why it seems odd to you that I'm advocating separation of business and application logic

And now I don't understand:

3. why "keeping data integrity and business logic close to the data is contrary" to
4. which "separation of interests that I'm advocating".

As for T-SQL being used for a purpose that it wasn't designed for, bear in mind that functions in C were at first not intended to be used to assign/retrieve values to variables, until C++ and the OOP paradigm became popular and it was decided that it is in fact important for data objects to be fully autonomous and guarantee valid data at all times at least on the executing thread.

Given a list of tables, can you guess which ones you can insert data into without breaking data integrity? On the other hand, if you were given a list of stored procs, given they are named meaningfully, you would know that these are the interfaces that the database was (surprise) designed to be used with. Ensuring proper use of the database outweighs abiding to intended uses of tools.

Your application will not necessarily be provided with the database, so if your application is non-existent to the next person who wants to program against the database, that person is in trouble. And even if it does exist, they have to rummage through your code and guess what special steps you've taken to ensure that the data is valid.

One thing about The Code Project is that everyone likes to hear the whys as much as the hows.

Not to beat a dead horse or anything, but I would have been less inclined to question the security of your code had you explained in the article or code why you had a dummy connection string with a dummy password, which you later explained that you expect none of your readers to follow such example. Think of the beginners who might have gone ahead and done the same thing!

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.1509028.1 | Last Updated 9 Oct 2007
Article Copyright 2007 by Nick Higgs
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid