This is clearly a data modelling problem - even if you do find a module that provides some kind of assistance, it wouldn't be flexible enough to handle those 'other constraints' nor can it remotely address the risk of design change your requirement represents.

My advice is that before even deciding what to implement in perl or SQL, you need to design and maintain your logical data model (here is a short course http://www.sum-it.nl/cursus/dbdesign/english/index.php3) and use that to drive what you then build in perl, DDL and/or SQL as your physical implementation.

At that point you'll have well-definied entities we can look at to advise on how to implement them.

Your requirement does suggest the event entity would be a parent that owns event-day children (as database tables) but I'd need to see the rest of the requirement to be confident about that - also I don't yet see why you want to use mathematical combinations which are different from the simple multiples concept your requirement so far suggests

Hope this helps,

Simon

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.