The problem with the first is speed and query building ... and the second hides that data away where it can't be easily queried.

Yup. I'm using metadata tables for cases in which most of the information is stored this way, and packed hashes for cases in which most of the data is in normal columns and only a few extras need to be packed away.

While I do think this technique is useful, I haven't yet found a way to abstract this into a general-purpose solution.

Both kinds of implementation are reasonably easy to code as a layer over one of the standard RDBMS-OO mapper frameworks, like Class::DBI or my own DBIx::DBO2.

In reply to Re: Re: Re: Re: Efficiency MySQL question by simonm
in thread [untitled node, ID 308077] by Samn

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.