[ Thanks to Kelley for this link.
]
“It seems everybody has their favorite persistence mechanism in
Perl. It goes with the territory–everybody has slightly different
requirements and therefore everybody needs something slightly
different. Tangram, Alzato, SPOPS, and more are all valid, capable
solutions to the problem of persistence in Perl, yet all share one
common factor–they store some sort of map, or schema,
somewhere.“These maps simply join the correct place in the database to the
field of the object that you require. From that you can recreate an
object from the database, or place an object from memory into the
database. A friend of mine once said ‘a schema is like a template,
only backwards.’“Having requirements set in stone doesn’t hinder you–the
database schema sits with the class, and you don’t need to worry.
However, if your requirements are going to change (and whose
aren’t?), then you’ll run into problems with having to change both
the map and the class. Additionally, I tend not to think in terms
of an RDMS, but in terms of objects.“Pixie offers a slightly different approach in the sense that it
doesn’t require a schema or map from the class to the database–it
just stores objects…”