Or maybe not. In any case, whenever I try to think of the solution to a problem that involves data, I seem to instinctively think of it in terms of an RDBMS table. My problem is that surely RDBMS systems aren't the only way to solve these problems, they might not even be the best way, but I can't think of any other ways!
As an example, I was recently designing a "forum" type system, similar to the one at perlmonks, where people would post nodes and replies and so forth. If I was doing this with a database of some sort, I would use a table with fields like: id, author, title, body, parent, date; indexed on author, id, parent and date, probably.
In the spirit of TIMTOWTDI, surely there is some other way that I could store this data, but I can't think of any!
(Note: I have no real problem with using relational databases to solve this type of problem, but since I instinctively reach for them all of the time now, I'm beginning to worry that RDBMSs are my hammer and every problem is turning in to a nail)
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.