http://qs321.pair.com?node_id=890211

skazat has asked for the wisdom of the Perl Monks concerning the following question:

Hello everyone,

I'm having trouble saving UTF-8 text using MLDB.

I understand that the value needs to be encoded on save and decoded before being used, but MLDB provides a additional problem, since you're not just passing a string to it, but instead a complex data structure - you cannot attempt to encode the complex data structure and think that's going to do the trick - it doesn't even make sense.

This means you probably need to encode/decode (at the right time) each value separately.

Is there any easy way to do this? It seems that you would have to walk through the entire data structure itself. Sadly, I don't know a bulletproof way to do that, in this instance. I do know the format of what to expect of this data structure, but it may change in time. Mostly, it's just a hashref of hashrefs, perhaps with some arrayrefs - no objects, or strange things like that.

Has anyone already stumbled on this problem?

Attempting to save a value with an unencoded UTF-8 string in one of values in a complex data structure using MLDBM will give back this error:

 Wide character in subroutine entry at ../perllib/MLDBM.pm line 161.

I'm using MLDBM with the FreezeThaw backend:

use MLDBM qw(DB_File FreezeThaw);

as using Storable:  use MLDBM qw(DB_File Storable);

produces this delightful error: 

 
Storable binary image v35.114 more recent than I am (v2.8) at blib/lib
+/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 421
+, at ../perllib/MLDBM/Serializer/Storable.pm line 27

[download]

Which makes very very little sense to me at all.

35.114? My brothers/sisters, I'm sincerely lost in the woods, with this one.

-skazat

Replies are listed 'Best First'.
Re: MLDBM and UTF-8
by ig (Vicar) on Feb 28, 2011 at 07:08 UTC

    Regarding Storable, the error message is indicating that the binary data it is trying to retrieve was written by Storable version 35.114. Since current version is 2.8, it seems most likely that you are trying to read corrupt data.

    I wrote a small test using Storable and it appears to work.

    use strict;
use warnings;
use MLDBM qw(DB_File Storable);
use Devel::Peek;
use Encode;
use FreezeThaw;
no warnings 'utf8';

$| = 1;

tie my %data, 'MLDBM', 'testmldbm' or die $!;

my $string = "a string with a wide character: \x{0100}";
Dump($string);

#my $fstring = FreezeThaw::freeze($string);

$data{string} = $string;

print "$data{string}\n";

    [download]

    It produced the following output, but cut-and-paste seems to have mangled the wide character. It looks like a capital A with a bar above it on my terminal:

    SV = PV(0x9766470) at 0x964eae8
  REFCNT = 1
  FLAGS = (PADMY,POK,pPOK,UTF8)
  PV = 0x97a5190 "a string with a wide character: \304\200"\0 [UTF8 "a
+ string with a wide character: \x{100}"]
  CUR = 34
  LEN = 36
a string with a wide character: Ā

    [download]

    Changing the script to use FreezeThaw, it reproduces your error. This appears to be a limitation of DB_File. Apparently FreezeThaw passes the wide characters through to DB_File while Storable does not.

    Maybe you can use FreezeThaw with a filter, something like the following:

    use strict;
use warnings;
use MLDBM qw(DB_File FreezeThaw);
use Devel::Peek;
use Encode;
use FreezeThaw;
no warnings 'utf8';
use Data::Dumper;
use DBM_Filter;

$| = 1;

my $db = tie my %data, 'MLDBM', 'testmldbm' or die $!;

print Dumper($db->{DB});

$db->{DB}->Filter_Push('utf8');
if($db->{DB}->can('Filter_Push')) {
    print "can Filter_Push\n";
}

my $string = "a string with a wide character: \x{0100}";
Dump($string);

$data{string} = $string;

print "$data{string}\n";

    [download]

    With the filter added, this test script does not produce the Wide character error - it seems to work.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom