Well it all depends on what type of usage you are expecting. If the pages are viewer agnostic, (No: Hi Lee! Welcome Back.) I would go static and generate the page when they actually update the record. If they are doing this from an app you are making, it should be trivial to catch changes.

If there's no real process (just using mysqladmin or something) You could run a query every couple of minutes and compare the timestamps to a "published" timestamp to see if it needs updating. Much simpler and less fragile. The less parts there are, the less parts there are to break IMHO. If you need real time inventory or similar embedded in the pages and they change constantly, then live is certainly the way to go.

As far as linkage, I would just make the id (page name) always the $product_code=~s/\W/-//g; $product_code =lc( $product_code . '.html'); Then there isn't any confusion on how to link to something. You could even "borrow" the bracketed linkage from perlmonks for internal links in the raw data and it would be simple to check the validity of local links when updating.

Personally, we use static pages for 95% of our work.

-Lee

"To be civilized is to deny one's nature."

In reply to Re: Database driven web content: live or tape? by shotgunefx
in thread Database driven web content: live or tape? by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.