Database table design vs. ease of use. (composite PKs?)?

I actually prefer the second option, with the ID column as the "surrogate" primary key. Most database gurus would probably say that you should look for the "natural key" in the table (which could be composite), but I think it's easier to work with single-column surrogate PKs, especially when using ORMs. Even if the ORM supports composite keys, it's still easier to work with a surrogate key.

It's also easier to write queries against tables that use IDs, as opposed to composite keys.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.