I have a very basic question about a database layout. I want to set up an
item rating application with a database backend. I was wondering wat the
most efficient database layout is.

• check this image for my current (basic) database plan

Any comments or suggestions are very welcome.

the rating table should not have its own id as PK

the PK should be a composite PK consisting of the two FKs

Thanks for that one Rudy, i think that's exactly what i was looking for. I always tought there was a 'official' way for this very basic DB issue. (i never read manuals)

Either way, you need a unique constraint on a set of logical values. Should this also be your primary key is up to you.

It's never too late to start. BTW, isn't "dutchstoner" a bit redundant?

It is redundant...

Heh... good to see someone still knows how to have fun.