Categories and sub-categories, best practice

I have an application which has a database table called Category. Its very simple, with fields id and categoryname.

My client now wants functionality for sub categories. Whats the best way to do this. My initial thought was to keep the same database table but have a 3rd column called ParentID which contains the ID of the parent category.

Is this the best way? Or something else.

Thanks

FORUM_CATS: cat_id, subcat_id, cat_title

then something like FORUM_POST: POST, CAT_ID, ect., ect.

Quote:

---

Originally Posted by MondeoST24

I have an application which has a database table called Category. Its very simple, with fields id and categoryname.

My client now wants functionality for sub categories. Whats the best way to do this. My initial thought was to keep the same database table but have a 3rd column called ParentID which contains the ID of the parent category.

Is this the best way? Or something else.

Thanks

---

As the previous poster so cryptically explained, you should use a second table for the subcategories that relates back to the category table. That's the normal way to design a relational database.

Your original table remains unchanged:

tblCategory
CategoryID (Long) <== Primary key
Descrip (String)

tblSubCategory
SubCategoryID (Long) <== Primary key
CategoryID (Long) <== Foreign key; relates back to tblCategory
Descrip (String)

my way is perfectly normal. Many php forums do it the way i do it.

Quote:

---

Originally Posted by psychotomus

my way is perfectly normal. Many php forums do it the way i do it.

---

As far as I can tell, we are both recommending the same approach. I was just offering more detail.

EDIT: On re-reading, I now see that you recommended a flat-file approach. I'm not a fan of that, no matter how many php forumns do it.

I didnt recommend a flat-file approach. i recommend 1 table instead of 2.

That's what flat-file means.

And it's not normalized, which is bad coding practice.

If you will only have one level of sub category then a second table is best. If you plan to have sub-sub categories and so on I think the parentID idea works better as it will alow and amount of sub levels.

I try to avoid recursive structures. I would use the two entities approach.

HoraShadow

I don't think I was suggesting you do otherwise. If you want to have an unlimited number of sub categories though you have no choice.