|
Tables and relations
|
Previous Top Next |
| · | Multi criteria search,
|
| · | Quick search,
|
| · | Calculated search,
|
| · | Sort,
|
| · | Export,
|
| · | Printing.
|
| · | No unnecessary entries : time saver
|
| · | No redundant information : space saver
|
| Relation 1 to N
|
| A couple may have several children, and own several cars.
|
| It would be more judicious to store the relative information of the children and car records in definite files, rather than in the couples file.
|
| For each couple, the number of records, in relation to cars and children, can be contained between O and N.
|
| It is difficult in this case to anticipate a record structure, "couple" integrated with the information 'children' and 'cars' without being at some time or other limited by the amount of anticipated information and penalising the place occupied beforehand.
|
| It would be in their interest to create a 'couple' file and two related files 'children' and 'cars'. The type of relation between the file 'couple' and the files 'children' and 'cars' is 1 to N.
|
| A couple may correspond N children and N cars. The 'children' and 'cars' records have been created through necessity.
|
|
|
| Relation 1 to 1
|
| One Contact record can correspond to one record in relation maximum.
|
| A contact has one social security card and only one.
|
| The large amount of information relative to this card is managed from the corresponding file.
|
| In this way if the person does not own a card (a child for example) no unnecessary place has been used.
|
|
|
| Relation N to N
|
| Take for example, keywords: A 'contact' record can be developed in an unlimited way by these hierarchical keywords.
|
| It is possible to link a 'contact record to several keywords. In the same way the same keyword can affect several 'contact' records.
|