"databases are harder to understand than simple nested data structures"
I would debate that (subject to the availability of cold beverages).

In most cases I have encountered, relational databases offer a simpler, more directly-mapped representation of the problem space, when compared to multi-level data structures, especially when it comes to traversing said structures to get summaries. I find OOP is required to approach equivalent simplicity.

I'm too lazy to substantiate that argument, so I'll just leave it there, and let you have the last word, should you so desire.

Cheers!

     Syntactic sugar causes cancer of the semicolon.        --Alan Perlis

In reply to Re^3: Aaaarghh...hashes of hashes..again :( by NetWallah
in thread Aaaarghh...hashes of hashes..again :( by viffer

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.