Arrays or extents (or what ever your RDMS wants to call them) are bad from a database design standpoint and should not be used, unless you have one helluva good reason (I personally have never had a good reason to use them, ever).

Extents break 1NF and are the equivalent of either:

1. Table CD: cd_name, artist, song1, song2, song3,...

2. comma delimited strings in fields

This makes for bad code - code which has to cover for bad database design.

So it is not a question of 'This can double the complexity of building your statements'. Array/extents will add unneeded complexity of your code, period.

An article on Database Normalization should explain why this is bad



grep
Mynd you, mønk bites Kan be pretti nasti...

In reply to Re: Re: Flexible Database Updates by grep
in thread Flexible Database Updates by jerrygarciuh

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.