On the Complex object...
On the surface, it seems unnecessary to constrain Complex [to encapsulate
primary keys] to only represent multiple entries (keys > 1). Consider the
possibility of an object retrieval service similar to...
// All our persistent objects are DaoObjects
DaoObject DBService.RetieveDaoObject(Class type, String uri)
...where the string represents the primary key such as "####|####|####"
[using "|" as our prototype delimiter]. The service implements a very
simple Complex parseUri(String uri) and passes on the work to load(...).
Some simple changes in assumptions made in ClassMolder, SQLEngine... were
required to test the concept.
We would like to submit it for design consideration (...How can we get
involved...). The above change makes for a simple lazy load design of
related/reference objects which we would also like to contribute (is there
another list for design and conceptual contributions)with some thoughts on
transactions.
David Mann
Invera Inc. Montreal
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
