Good coding practice ???

[eluser]Chicken's Egg[/eluser]
[quote author="xwero" date="1215792168"]I would spit the database table in blog and news and then you also can add fields one section requires and the other one doesn't. For instance adding a traceback id to the blog table.[/quote]
I would do that too, but suggest to split the content of the news- and blog-postings from the meta information. So, one table for pages (using the nesteds sets pattern). One table for the content of the blog-postings and one table for the content of the news postings.

Advantage:
- It becomes easy to create a menu or a sitemap of your website, as all pages can be found in one table.

Disadvantage:
- I haven't got a clue how to create the urls in the menu to manages this all. It's something I'm struggling with a couple of days now.