On Dec 7, 2006, at 7:08 PM, Guyren Howe wrote:
I can see the advantages of using a Factory object, but a lot of
my objects contain instances of other minor objects (e.g. an
Address is it's own object in this setup, and each Customer Object
has an Address Property), and the first option makes this easy by
allowing object creation to cascade automatically up the tree
simply by creating the root object.
I would say go Route 2, but this will depend on the particulars of
your application.
I tackled this recently, so I will pass on some related information.
Further to my last post, I should mention that Operator_Lookup is
very helpful: you can have a generic database superclass present the
fields of the table as properties without you having to explicitly
write code for each one. This will also let you write code to track
which fields have been modified so you can write them back to the
database.
Regards,
Guyren G Howe
Relevant Logic LLC
guyren-at-relevantlogic.com ~ http://relevantlogic.com
REALbasic, PHP, Ruby/Rails, Python programming
PostgreSQL, MySQL database design and consulting
Technical writing and training
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
