In my experience, I have come across very few problems that cannot be served by a relational database. Sometimes there is massaging involved, mostly when serializing data structures. Of course, that will have to be done with an Object database as well -- I am not aware of any popular disk storage mechanism that does not store information as a stream of bytes. At some point, someone will have to write a layer to serialize data.
I find myself using DBI because it's quick, it's easy, and knowing it, I can work with many database backends with ease.
In the future, I may need to use another approach, depending on the project. I don't really care if Wall Street claims that wearing ties makes me a better programmer, either.
If writing join statements is too painful, perhaps you or someone else will write a tiny bit of syntactic sugar to define a common 'object', using foreign keys or whatever, performing that abstraction for you. I highly recommend abstracting away nasty details of that sort.
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.