[thelist] MySQL as CMS

[Mike Migurski]

>Are there any faults in this approach that I am not seeing?

No, but the devil is in the details, as usual.


>This will not be a particularly high traffic site, so I am not concerned
>about taxing the data base.

Taxing the database might not be as bad a problem as you think - we've
built a similar system, and all the database query functions (as well as a
few others) have built-in caching mechanisms that store the results, in
php's serialized form, in temporary files.

The difficulty is getting the cached versions to properly reflect the
contents of the database, etc. etc. I've seen other companies include
manual "flush cache" functionality on their CMS interfaces, but this was
deemed a hugely inelegant solution - the engineers demo'ing the software
managed to forget to flush the cache a bunch of times themselves.


---------------------------------------------------------------------
michal migurski- contact info and pgp key:
                 http://www.saturn5.com/mike/contact.html

                "Freedom! Horrible, horrible freedom!"