Yes, it's certainly possible to let have a dependency on the
storage method in your design. I won't say this is bad, but
it's not how I would do it. I would do the design of the backbone first, and have it not tainted with storage method.
The problem with that is that it's harder to switch to a
different storage method (and I don't mean switching from
YAML to Data::Dumper, but switching from flat files to DB files, or somekind of database), because the storage method
is too much wired in. If the storage method is an 'add-on',
it's easier to replace.
As for this particular problem, several methods have already
been mentioned. Writing down a comparison between all the methods would take too much of my time - the OP can do some
work as well, and download the various modules and read the
documentation.
But you are free to write an article, comparing the various
storage modules, and how they are more or less useful in
the project the OP is undertaking.... ;-)
Abigail
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.