Storable

Storable is ok for short-time storage, e.g. caching stuff that needs a long time to be recalculated. But DBI sounds like long-time storage. OS, platform, and Perl versions may change over time, and because Storable depends on all of these, that will break Storable.

Stuffing serialised perl data structures into a database does not sound sane. It means the database is not normalised. Ideally, all data would be stored in database-native formats.

Anyway, there are various other formats to serialise data structures that do not depend on the exact perl version, e.g. XML, JSON, YAML.

See also:

• Re: Perl Storable problem (i Think)
• Re^2: memory persistance
• Re^3: Portable datastore formats in core perl?
• Re^4: The safety of string eval and block eval.
• Re^2: Storing state of execution
• Re^2: Caching Format

Alexander