Shown here is the application that generates CObject and CObList derived classes for Object-Oriented database management.

Some of the projects I have been working on lately have made extensive use
of CObject derived classes for encapulated data management (Object-Oriented Databases). After
creating only a few data objects, you begin to realize that the production of much of the code
could be automated. This project is a code generator to produce CObject-dervied data classes
with serialization and protected data members.

In addition to the CObject derived data classes, the application can also generate a sorted CObList
derived class to hold your data objects. For each data object you create, you can specify index
members. The list of objects is then sorted by these index members. When you add a new object to
the list, the CObList derived class ensures that it is added in the correct position in the list.

Features of this code generator:

Produces CObject derived classes, and CObList derived classes to hold the objects in a sorted list

Class name follows the selected file name

Variables are assigned data types based on Hungarian notation prefixes

Includes Serialization code

All data members are protected and accessed with Get/Set inline functions

Includes initialization code in constructor

Includes member function to duplicate the properties of an object

Includes last modified date/time

Includes Dump and AssertValid functions

Object list can be sorted on multiple fields

Limitations of the current version:

Currently, you can only create one "key" value, although with a little trickery, your could run the application multiple times to generate multiple CObList derived class and allow multiple lists.

If you change the value of one of the key fields, the list does not resort. Although it would be a simple matter to add a sort function to the CObList derived class, the difficult is that there could be multiple instances of the CObList derived class throughout your application, all containing pointers to the same objects. So if one object changed a key field, you have to resort all those lists. The question is how best to keep track of where all those lists are. I don't have an answer for that yet!

The function to add a new object to the list is not well optimized for the sorted list

There is no copy constructor

To use the code generator:

1. Select a file name for the source file output. Your header file will have the same name but with an ".h" extension. Also, the class name is derived from the file name such that Example.cpp will produce a class called "CExample", and the COblist derived class will be
CExampleList. Note that the code generator will overwrite any existing files.

2. Enter the names of the data members for the class. Data types are determined
from the Hungarian notation prefixes. The program uses the following prefixes (these are easy to change):

dt -- COleDateTime

str -- CStirng

n -- int

f -- double (not FLAG!)

b -- BOOL

rgb -- COLORREF

If you want to generate a CObList derived class to hold your objects, enter Index members for the class. These will be added to your CObject derived class. The list will be sorted by these members in the order in which they appear. The indeces will also be used for comparing objects, and will available as parameters in a constructor.

If you leave the Indeces list blank, the application will not generate a CObList derived class. Only the CObject derived class will be generated.

3. Click the "Generate" button to generate the source file and header file.

The code generator produces code using my own programming
style so you may want to adapt it to more closely follow your own style.

So that's it. I am somewhat new to OODB, so I am interested in feedback and improvements.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

Share

About the Author

Bob Pittenger is founder and President of Starpoint Software Inc. He holds a B.A. degree from Miami University, M.S. and Ph.D. degrees from Purdue University, and an MBA from Xavier University. He has been programming since 1993, starting with Windows application development in C++/MFC and moving to C# and .NET around 2005 and is a .NET Microsoft Certified Professional Developer.

Bob is the author of two books:
Billionaire: How the Ultra-Rich Built Their Fortunes Through Good and Evil and What You Can Learn from Them
and
Wealthonomics: The Most Important Economic and Financial Concepts that Can Make You Rich Fast.
Visit http://www.billionairebook.net for more information.

Comments and Discussions

Well, I can tell that not a lot of people have been interested in this code and that is too bad, because two years later, I am starting to think this is one of the smartest things I ever did.

Since this article was posted, I have enhanced the generator to create database objects, and collection classes to hold them. I can't repost it because there are a lot of proprietary dependencies in the code, and the generator no longer produces code that compiles without modification.

Since this article was written, I have used variations of this object oriented design in two commercial applications. What have I learned?

1. An object oriented design has a lot of advantages, but the biggest disadvantage (as implemented here) is the inability to have data accessed by multiple users on a client-server architecture.

2. Another disadvantage is the time it takes to allocate all the memory for all the objects when reading files and updating pointers. Speed was definately a problem.

3. I ditched the pure OO design, and went to a relational design for an update to one of the commercial products. You'd think this a difficult task, but the good OO design, and the already existing objects made it relatively easy. The point is, it works VERY WELL to use an object oriented data design running over top of a relational database. There are so many advantages, it is hard to list them all here (besides, I doubt you are reading this anyway). The only disadvantage was really speed, and a little bit of akwardness reading rowsets from queries.

4. The idea of a code generator saved many many many hours of tedious repetative coding. I can not quickly whip together database schemas for complex objects, generate the code, and whip the whole thing together in an app. It is well worth your time to write code generators if you think you will be in this situation.