I don't think he wants to start fresh each time. He wants to save the data so he can display more than one line.
It looks like a CGI script that wants to accept a line of chat, then display the previous 10 lines. What it actually does is this:
- deletes all previous messages
- creates the db file, ties %chat
- unties %chat, thereby not storing any messages
- accepts a new message
- displays the last 10 messages (which were just deleted!)
Not only is the %chat untied from the the DB_File when it's tied to TIE::IxHash (as you pointed out), the script is deleting the DB_File every time it is hit. | [reply] |
-sauoq
"My two cents aren't worth a dime.";
| [reply] |
| [reply] |
I must be able to tie %chat to both objects otherwise it's uselessPretty strong words, partner ;-) I think what you mean is that to pull this off you must be able to represent the data in a sorted manner.
First off, sauoq was right on about IxHash. Second, diotalevi says to use $DB_BTREE. An excellent suggestion, as long as you use a sensible key - maybe date/time stamp - and be aware of the possibility of duplicates. It will always be sorted - it's stored in a balanced tree. The key your script uses is $cnt, but I don't see it being initialized anywhere (probably not a sensible key ;). Every message is stuffed into the same slot, overwriting the previous message. The most straightforward short-term solution for you IMO would be to use $DB_RECNO like so:
# tie your array to the file
tie @chat, 'DB_File', 'chat', O_CREAT | O_RDWR, 0644, $DB_RECNO;
# push the message info onto the array
push @chat, "Message number $_" for (1 ..20);
# print the last five messages
print join "\n", @chat[-5 .. -1];
__END__
output:
Message number 16
Message number 17
Message number 18
Message number 19
Message number 20
You'll be able to treat @chat like an ordinary array. As a bonus, you'll be able to view or modify the chat db file with any text editor.
| [reply] [d/l] |
| [reply] |