Storable binary image v5.39 more recent than I am (v2.6)

[jithint]

Hi Monks, I'm using Storable module to store and retrieve data structures. When I run the script I get this error:

"Storable binary image v5.39 more recent than I am (v2.6)"

What does this mean and more importantly, is there any way to get around this? I found another thread here regarding this but it wasn't much help :(. Any help is appreciated.

[keszler]

That message comes from Storable.xs, in the *magic_check function. The current version of Storable is 2.21. Internally it defines STORABLE_BIN_MAJOR and STORABLE_BIN_MINOR as 2 and 7 respectively. (So your v2.6 would be a slightly older version of Storable.

The 5.39 comes from the Storable file you're trying to read. Since Storable hasn't gotten close to setting 5.39 as a version, I wonder if the Storable file was created on another system; one with incompatible byteorder or integer-long-pointer sizes.

[Anonymous Monk]

Hi I am getting the similar error, Please let me know how to fix it? Error: Storable binary image v34.114 more recent than I am (v2.7) at Storable.pm Thanks Dandu

[Anonymous Monk]

upgrade Storable to matching version that reads the file, upgrade storable all around, make sure you're using nstore, move away from storable to a text only format like JSON/YAML

Which of these solutions do you have trouble using?

[Anonymous Monk]

You should upgrade/downgrade Storable until you find a version which will read your file, then serialize to ascii based format (like JSON), then install latest Storable (or your preference) and import your data back

Burned by Storable

[jeturcotte]

Suddenly happening to me today, albeit "Storable binary image v61.34 more recent than I am (v2.7)" ... 61.34! Oddity being everything was fine yesterday and only thing I'm aware of having been done was the dev mysql server being restarted (the Storable'd content being in a field in a table there.) This is of no help to anyone, but now I'm searching for comprehension myself.