Re^3: Can I serialize an object and have it remember it's type?

Be forewarned - Storable does not provide forward/backward compatability. That is, if you upgrade your perl, there is a significant chance that all your stored objects will be unretrievable. If you switch platforms, it's almost guaranteed (use nstore - that may help).

At least, that was my experience with Storable, oh so many years ago. I'd be happy to hear that has changed.

Comment on Re^3: Can I serialize an object and have it remember it's type?

Replies are listed 'Best First'.
Re^4: Can I serialize an object and have it remember it's type? by cowboy (Friar) on Jul 21, 2005 at 17:28 UTC
We use storable extensively on many different systems with very little trouble. Version problems are potentially still there, but only if a newer version stores a data type that an older version cannot handle. (it now will try to handle the data from the newer storable instead of just croaking) I second your comment about nstore though. I'd highly recommend using nstore by default. Having to convert a couple million stored objects because you add a 64bit machine to your farm of 32bit machines sucks.	[reply]

Replies are listed 'Best First'.

Re^4: Can I serialize an object and have it remember it's type?
by cowboy (Friar) on Jul 21, 2005 at 17:28 UTC

We use storable extensively on many different systems with very little trouble.

Version problems are potentially still there, but only if a newer version stores a data type that an older version cannot handle. (it now will try to handle the data from the newer storable instead of just croaking)

I second your comment about nstore though. I'd highly recommend using nstore by default. Having to convert a couple million stored objects because you add a 64bit machine to your farm of 32bit machines sucks.

[reply]