I'm working on a simple CMS/Blog system for Bands, and I'm stuck on a question of table design...

For example, I initially create the tables article, album, and photo for a band to store that data. If I want to add the ability to comment on these and any other items (like facebook provides) what is the best practice for creating the table(s) necessary?

Is it reasonable (possible) to make a single comment table to hold all comment data for all other tables, and if so how should I go about keying this to the parent tables?

Otherwise, should I resort to making multiple tables, article_comment, album_comment, etc., etc.

I just want to maintain extensibility and manageability, so that down the line if I add an audio, or whatever table, it can easily be integrated.