[PEAK] peak DMs and model element component hierarchy

Doug Quale quale1 at charter.net
Fri Jul 16 23:04:53 EDT 2004

Looking at the wiki IntroToPeak example and the bulletins example
included with peak itself, it looks like the Data Manager examples
create model elements whose parentComponents are the DM instances that
created them.

Does it make sense to go to extra trouble in the DM to make the
parentComponent for a model element be the model element it is
included in, or is this pointless or harmful?  With a model like this

    class Database(model.Element):

        class tables(model.Sequence):
            referencedType = 'Table'

        class views(model.Sequence):
            referencedType = 'View'

should the Table and View model objects included in a database object
have that database as their parentComponent?

More information about the PEAK mailing list