Well, they both work, so the main thing to do is flip a coin, implement one and move on. :-)

But in the spirit of waffling on, try thinking about the thought processes of a future maintainer. How likely are they to break things (and how serious is it if they do)?

One thing which you can end up doing a reasonable amount of on a live system is going in with the SQL prompt and taking a look. There's something to be said for having a data model which allows you to run ad-hoc queries without too many joins.

Another way of breaking the deadlock might be to think about if you choose either approach, how easy would it be to switch to the other (when you've got a bunch of live data)?

In reply to Re: [OT] When coders don't see eye to eye by jbert
in thread [OT] When coders don't see eye to eye by Anonymous Monk

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.