Re^2: Disk based hash (as opposed to RAM based)

[thomas895]

in reply to Re: Disk based hash (as opposed to RAM based)
in thread Disk based hash (as opposed to RAM based)

One way around the limitation would be to store your array values as joined strings:

That works for simple strings, but once you get to more diverse strings, you should probably consider a serializer. I find that JSON::XS works great for this purpose, as does Data::Dumper with an eval. The latter method may not always be the best choice, though. JSON is more portable and can be read by another non-Perl application more easily.
For example:

# Using JSON::XS
use strict;
use warnings;
use DB_File;
use JSON::XS qw( encode_json );

my %hash;

unlink "tempfile";    #Remove previous file, if any
tie %hash, "DB_File", "tempfile", O_RDWR | O_CREAT, 0666, $DB_HASH
  or die "Cannot open file 'tempfile': $!\n";

while ( $sourceString =~ /example(key)regex(value)example\b/ig ) {
    my $key   = $1;
    my $value = $2;
    my $string_to_insert = encode_json( [ $key, $value ] );
    push( @{ $hash{$key} }, $string_to_insert );    #Push the value in
+to the hash
}

#And then use decode_json() from JSON::XS somewhere else to get an arr
+ay of your values.

HTH

[BrowserUk]

I realise that you are trying to be helpful; but I do not think you have thought this through.

• Firstly, the OP clearly states Hash of Arrays.

  Hence, catering for anything more is overkill.

• More importantly, the OPs code clearly shows that he needs to build up the arrays piecemeal -- ie. value by value.

  If he were to use a serialiser module for this, he would need to deserialise the current state of the appropriate array; add the latest new element; and then re-serialise; for each line in the file. Which would be horribly slow no matter which of the serialiser alternatives he used.

  The only other alternative would be to wait until each array was complete in memory before serialising and adding to DB_File, but that would mean waiting until the entire file had been read, and thus, the entire structure would be required to be hend in memory before serialisation could be performed. And if he had the memory to do that, he wouldn't be looking to use a disk-based hash.

For a one-off process, he might consider pre-sorting the input file by the key field, so that the contents of each (sub) array could be built up in memory before being serialised once, but for that to be a viable option requires a whole set of circumstances that are not in evidence from the OP.