DB Schema Proposal Round 6

[cbrumbaugh]

@luap42

Wouldn’t it be better to add a column called internal_name (or _id) that will be queried by the software. I think something like WHERE internal_name = 'may_suspend_all_the_bad_people' is better to read and understand than WHERE id = 42 .

I would rather not, I think the ids are just fine. Maybe others have a different opinion, but I don’t see the need.

@luap42

member_privilege

I’d go away with this table and rather split it into two tables, which are:

Why? Is it faster?

@luap42

post_type

I’d add columns, such as:

I would rather have these be enforced by the software instead of the DB

@luap42

status

For things like protected/locked/closed

@luap42

post

We don’t need an is_meta as said before, but instead a category.id reference. I’d also add the following columns:

I would rather have foreign keys than booleans. Also, can a post have multiple notices? Like both closed and locked?

@luap42

We need to have tag sets (as said below). I’d recommend adding a tag_set.id ref and a tag_set table with id and display_name

I would rather do tag groups by a parent_id column that links back to the top level tag.

@luap42

post_vote

Add date fields.

All that’s needed is the create date and the modified date, those columns are on every table.

Your suggestions that I agreed with I incorporated here DB Schema Round 7