I agree that repson has it right, if using a relational database, take advantage of it's strengths and create a second table for the many in your one->many relationship. Then you can take advantage of foreign key restraints which can help keep some rogue code from messing with the relationships, adding descriptions to prod_id's that don't already exist in the parent table.

Another simpler option is to remove the unique restraints on Prod_id and just add multiple rows to the table. you'll get the same data back from a select on prod_id as you would using a join. the downside is space... if that is an issue, then use the two table approach.

so Postgress has an "array" type?

In reply to Re: DBD::Pg INSERT enlightenment by wardk
in thread DBD::Pg INSERT enlightenment by penguinfuz

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.