In terms of database design, class design, and many other programming tasks, it is often useful to restrict your concept of numbers to there being only three numbers
That is a good rule of thumb, but it is just a starting point. The real rule is, in my mind, whether a data rule requires it; and if it does, how many. If how many cannot be answered with a specific number, a new (child) table is used for them. Otherwise, same table.
For example, if storing email addresses and one alternate, it may make sense to store both email addresses in the same table. Another example (from my current project), if you have an entity created with up to 12 parts (each part being similar to a level), it is likely better to store the 12 parts in the same table.
Technicalities, perhaps. But, this is what i do for a living.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||