The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Database Schema for my new site

I've just finished a logical database schema for a new site I'm working on (avatars2go.com).

People can join the site and upload avatars and let other people comment on them, download them, etc. etc. standard stuff right now really. Anyway, I'm trying to make the db as robust a possible, so I can easily add stuf without having to worry about th db much.

What is 'status' used for? Why is it tied to users and comments? Is it really many-to-many (can a user have many statuses assigned to them?)?

Comments, if I am reading your description correctly, are not many-to-many. You won't have a single comment being paired up with many images and vice versa, so the image2comment table seems redundant (store an imageID in the comment table?).

numofimages is denormalized -- is that necessary? Same thing with numberrated in image table.