a relationship which is obligatory on the 'many' side

[ngoz1]

hi everyone,
im new to this group

My question is -"If i want to create a one to many relationship between two tables. and i find that the many side is non obligatory
( i.e optional), do i need to create a join table between them? or is that just for many to many relationships"

 

[petersdaniel]

A one to many relationship join is not necessary unless you want the following:

- You want to maintain a tight relationship between the one record and the many. By adding cascade delete / update options, you can ensure that if records are changed or deleted on the one side, the changes and/or deletions are reflected on the many side.

- Relational joins aid in the quick development of query objects, ensuring that keys are appropriately linked petersdaniel@hotmail.com
"If A equals success, then the formula is: A=X+Y+Z. X is work. Y is play. Z is keep your mouth shut." --Albert Einstein

 

[ngoz1]

i think you may have misunderstood my question( though you also cleared some confusions i had about cascade joins)
let me rephrase my question:
i read some where that :

a sperate relationship table is required for any many to many relationship(which i agree with)
i also read that for a 1:m relationship - if the many entity type is non obligatory you must also define three tables(ie one table for each of the entities and one for the the relationship- this is the table i was referring to, as the join table) -is this true or rather necessary!!!