Schema design: many to many plus additional one to many?

Thus is a perfectly fine design. It is not uncommon for a junction table (AKA intersection table) to have attributes of its own - such as joining_date and that can include dependent tables. There is, as far as I know, no special name for this arrangement.

Thus is a perfectly fine design. It is not uncommon for a junction table (AKA intersection table) to have attributes of its own - such as joining_date - and that can include dependent tables. There is, as far as I know, no special name for this arrangement.

One of the reasons why it might feel strange is that these tables frequently don't exist in a logical data model. At that stage they are represented by a many-to-many join notation. It's only when we get to the physical model that we have to materialize the junction table.(Of course many people skip the logical model and go straight to physical.).

Thanks for your feedback! I've had a junction table with a few extra columns, but never had one with dependent tables so I just wanted to make sure there wasn't a pattern I've missed somewhere. – azymm May 5 '10 at 17:48.

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.