Now some people on the team want to split this common table into several tables, and one for each type of item. To me that is absolutely unnecessary

...

I believe my design is correct in both cases, and I also believe those are common issues to lots of monks. But other than knowing what is right, I also need to show evidence that what I am doing is common practice and there are theoretical papers/books/TERMINOLOGIES/web sites behind, otherwise the discussion can go on for quite a while...

So um ... you've decided that your way is best, but you have absolutely no proof of it, so you want someone else to give you evidence of why your way is better?

I'm not sure if this is just complete trolling, or if you're serious. If you're serious, I suggest you give up, and listen to the others on the project. Your solution may functionally work, but it's not going to scale well. I suggest that you come up with the questions that you need to ask of the system, and then both you and the other person come up with solutions -- the other person's will likely be simpler, run faster, and can be more efficiently tuned (less overhead from useless indexing, more compact tables, etc.)

As for references, the best one I have is the Oracle Data Modeling guide, but I don't think it's available unless you take the class.

In reply to Re: (OT) Couple of Data Model Design Considerations by jhourcle
in thread (OT) Couple of Data Model Design Considerations 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.