My rule of thumb is if you've gone to all the trouble of getting a database connection (often the most expensive operation) you might as well use it. Let the db do all the heavy lifting, it doesn't mind.
I often find that for reptitive data a long thin table wins over a short fat one. Everything gets easier. For what its worth my money would be on klassa's multi-row version
Rather than update the data you could simply add a new "set" with a unique key, which, in another table could be related to, say, a user and a date. A retentive web admin would then have lots of historical data with which to bore the pants off everyone. (charts, graphs, top 10s, oooo!) :-)
And if, say, you're using something like an HTML::Template loop to display your data you'll be looking for an array of hashes which the mighty DBI is happy to provide.
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.