BerkeleyDB, you've got exactly one index per file.
You could fake extra indexes, but you'll have come up
with "one to many" relationships - you may find "chevy"
in the "brands" index, but it can't refer to any single
other record - it has to refer to multiple other records -
which is ok with a RDBMS, but a pain with .db files.
If you make a linear search through the .db file every time,
performance should be ok for no more then a hit a second,
but will be slower then doing a linear search through a
flat file. With a hashed file, you access the records
randomly when you do a "linear" search, but with a flat file,
a linear search really is linear. I wouldn't have any
reservations at all about doing...
EACHREC: foreach my $rec (keys %tiedhash) {
foreach my $criteria (split / /, @searchkeys) {
next EACHREC unless $rec =~ m/$criteria/;
}
print qq{
$rec $tiedhash{$rec}\n};
}
or something thereabouts...
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.