J
Josh McFarlane
If this is not the right place to post this, I apologize.
I've taken over work for a few utility programs for a collection of
database / raw files. All the programs but one read from the files, and
as it is, many of the operations are done through standard non-OO code.
All of the database information is currently stored in linked list
structures. I'm looking to move the entire thing to objects.
I'm defining generic database, table, and record classes, as well as
base functions for the classes. Then I will define a specialized record
class for each table and populate members inside the database class
accordingly.
This is the first time I've really tried to dig deep into OO with C++,
so my question: Is this the right way to approach the design or is
there a better method for C++?
My overall goal is to standardize the code so when database design
changes, all I need to do is modify the generic database classes and
push those changes to the programs.
Thanks in advance.
Josh McFarlane
I've taken over work for a few utility programs for a collection of
database / raw files. All the programs but one read from the files, and
as it is, many of the operations are done through standard non-OO code.
All of the database information is currently stored in linked list
structures. I'm looking to move the entire thing to objects.
I'm defining generic database, table, and record classes, as well as
base functions for the classes. Then I will define a specialized record
class for each table and populate members inside the database class
accordingly.
This is the first time I've really tried to dig deep into OO with C++,
so my question: Is this the right way to approach the design or is
there a better method for C++?
My overall goal is to standardize the code so when database design
changes, all I need to do is modify the generic database classes and
push those changes to the programs.
Thanks in advance.
Josh McFarlane