I know it's late in the lifecycle , but I fear you need to get your data modelling right first and then map the entities to objects after that. I would advise producing a Bachman diagram before and after the change (I'll enhance that wiki later today - it looks too bare). Here is some very old documentation but which reasonably illustrates the use of this type of diagram in data modelling http://h71000.www7.hp.com/doc/82final/6393/6393pro_020.html.

Try to reduce your entities to one-to-many relationships, even where they are many-to-many in nature. That is done using a link table. Make sure all entities have primary keys and all child entities have a foreign key per relationship in which they are the many entity. Types (e.g. in your case notice type) are also a parent entity where the notice itself is the child. An entity maps to a concept like type, not just the objects in the real world. When your model is expressible as a connected network of one-to-many relationships then you are ready to translate it into objects. Hope this helps :)

__________________________________________________________________________________

^M Free your mind!

In reply to Re: How to implement set-style membership lists in my obejcts by Moron
in thread How to implement set-style membership lists in my obejcts by clinton

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.