[eluser]slowgary[/eluser]
Is there an industry standard way this is done? What do the big popular CMS packages do?
If markup is fine to store in a database, I'll still need to filter for html entities that are NOT part of an html tag, and I would probably do this on the way into the database or as part of the html editor so that it only needs to be done once, as opposed to on every page load.
Other questions still linger in my head, like searching pages. If the database stores the page with markup, how would you go about a user search function? If a user types <p> into the search, is it going to return all pages because it searches the page's markup too?
What about compression? Is storing this markup in the database a bad idea to begin with? I did some google searching and a few people suggested storing pages outside the database as individual flat files. That seems stupid to me though because they're both stored on a hard drive, except with a flat file you lose all the benefits of SQL.
I know this might seem like a stupid topic but I'd really love to figure out the 'BEST' method.