Mapping objects into rdb

From: Johan Nilsson <jni_at_esrange.ssc.se.--->
Date: 1999/02/17
Message-ID: <36ca7798.0_at_d2o19.telia.com>#1/1

  {Some of this is off-topic for comp.lang.c++.moderated, but it   could lead to useful discussion about "practical C++" and   "design patterns" topics. Please redirect database- or platformspecific    followups to the appropriate newsgroups. Thanks. -mod}

Hi,

I'm designing a system where the objects' data need to be persistently stored in a rdb (Oracle8). For compatibility reasons with existing systems,
I cannot use an odb. I'm doing the development in C++ and likely COM/DCOM. The database will not be some kind of enterprise system, it will be more of
a technical application with very few users at a given time directly connected to the it. Much of the work will take place in the context of a
few services/daemons which will communicate with the rdb, clients might (indirectly) use COM/DCOM for this.

Does anyone have any experience on this? Is there any applicable design patterns?

I would like all access to the database to go via the objects in the system
(except for generating reports etc) and have a few initial wonderings :

• How do you design the connection between the objects and the database?
• The users of the objects should not have to know that they are stored/mapped into a rdb. How do you decide when to update the rdb from within the object?
• How would you use transactions?
• How do you implement collections of objects, which represents rows in the database? Efficiently? .....

If you have any experience in designing and implementing a similar system,
please share it with me.

TIA, Johan

---

If replying by e-mail, please remove the spam protection '.---' from the end of my return address.

      [ Send an empty e-mail to c++-help_at_netlab.cs.rpi.edu for info ]
      [ about comp.lang.c++.moderated. First time posters: do this! ]

Received on Wed Feb 17 1999 - 00:00:00 CET