localtime in scalar context returns a string something like "Fri Jul 18 23:35:45 2003" which won't sort cleanly. Build the key like "YYYYMMDDHHMMSS" and the keys will be sorted on disk.
#!/usr/bin/perl
use strict;
use warnings;
use DB_File;
unlink 'db'; # to prevent dupes if this is run more than once
tie my %hash, 'DB_File', 'db', O_CREAT|O_RDWR, 0644, $DB_BTREE;
print "Building \%hash...\n";
$|++;
for my $count (1 .. 50) {
my @time = localtime;
my $key = $time[5] + 1900;
$key .= sprintf "%02d", $time[$_] for reverse 0 .. 4;
print "$count... " if $count % 10 == 0;
$hash{$key} = "Message number $count";
sleep 1;
}
print "Output:\n";
print "$_: $hash{$_}\n" for keys %hash;
Check the output, you'll see what I mean. The keys come out lexically sorted - the messages go from Message #1 to #50.
Remember that you can have duplicate keys with $DB_BTREE. If two values are inserted with the same time stamp, there's no guarantee which way they will be retrieved (which is why I suggested $DB_RECNO).
HTH
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.