Yes you can improve on that performance - if you are using
an object oriented database or something like DB_File.
(With some sort of threading of keys - MLDBM is not the
best of approaches either.)
Otherwise the fact that hierarchical data structures do
not map well onto relational databases will kill you.
And firing repeated queries against the database (a very
obvious guess) is really bad.
You can beat what they do though, but not portably. And
the way you do it is to create and populate a temp table
on the fly with a stored procedure. Works except that
all of that is mumbo jumbo that some databases (very
specifically MYSQL) doesn't understand, and which tends
to be non-portable from database to database.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.