Having an OODB would be great, but I wouldn't want it to be using persistent
objects though as that means that only the published properties get saved.
What if there is a private attribute of a class that I want saved? An
internal state variable for instance, I don't want to have to make it
published just to save it. I would want to keep it private in keeping with
normal OO methodology.
Nahum
-----Original Message-----
From: Dennis Chuah [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 23 September 1999 09:00
To: Multiple recipients of list offtopic
Subject: RE: [DUG-OFFTOPIC]: DELPHI WISH LIST
What I would like to see is an object oriented database integrated with
Delphi. Better still, an object oriented DB layer that can use ADO as the
backend. Persistent objects and their properties would automatically be
saved into the database. Data aware controls would be replaced with model
aware controls.
Dennis.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
