I think grep & I agree that using the array mechanisms
of RDMSes is usually a bad thing.
I disagree that "Array/extents will add unneeded complexity"
to your code period.

I do believe that fixed size arrays can be and often are
best put in a single record. Some examples are so often
done that they are invisible.

First, middle, and last- names are an example that could be

create table name (
   id   keytype,  -- constrained to parent
   seq   integer, -- place in name set
   name text
);

[download]

but who wants to deal with that?

The usage of address_line_1 and address_line_2 can be
viewed as an array embedded in a record.
Financial applications show arrays for the 12 or 13 months
of the year.
I used a pair of arrays to describe a set of items. There
could be upto 5 dimensions & 5 dimension_names.
All of these belonged in one record.

That the fullname or address should be one field is a
excellent alternative, but not always do-able.
Printing envelopes with a single address string may
be problematic.

Using a single fullname may induce the use of a nickname,
possibly recreating the initial issue.

The solution that I am currently implementing/trying is
to use arrays on the Perl side and separate fields on the
SQL side. A naming convention maps $o->{elem}[0] to elem_0,
and $o->{address1} to address1.

In reply to Re: Re: Re: Flexible Database Updates by rir
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.