Databases
StackOverflow2013
Postsdbo
POTrouble thawing data structures stored with Storable::nfreeze?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTrouble thawing data structures stored with Storable::nfreeze?
    text
    copied!<p>I have a bunch of data stored in a single column in a MySQL table. I have access to the ~5 year old perl code which stored it there &amp; can see that it is all hashes which were frozen with <code>Storable::nfreeze</code> before being stored. The MySQL column is <code>TEXT</code> and the table is set to <code>latin1</code> encoding. I'm now trying to retrieve this data back out for a one-off export. I know the app was originally running on perl 5.8.x, so I'm attempting this with perl-5.8.8. Unfortunately, I don't know what version of Storable was used.</p> <p>I first attempted using the most recent Storable, 2.39. That gives me:</p> <pre><code>Storable binary image v32.32 more recent than I am (v2.9) at perlbrew/perls/perl-5.8.8/lib/5.8.8/darwin-2level/Storable.pm line 417` </code></pre> <p>With Storable-2.14 I get</p> <pre><code>Storable binary image v32.32 more recent than I am (v2.7) at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 363 </code></pre> <p>With Storable-2.13 I get</p> <pre><code>Storable binary image v2.7 more recent than I am (v2.6) at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 363 </code></pre> <p>The unreasonably high binary image numbers in >= 2.14 make me think there's some change with how the numbers are being parsed. I believe this code was probably running on a 32bit OS, and now I'm trying this on a 64bit machine, could that be relavant? Next up is I'm going to attempt running a diff between 2.13 &amp; 2.14 to see if I can figure out what's causing the change.</p> <p>Any guidance anyone can give?</p> <p>Thank you!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload