This page (revision-40) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
40 26-Nov-2021 10:22 11 KB Karen Parrott to previous
39 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
38 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
37 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
36 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
35 26-Nov-2021 10:22 11 KB rforbes to previous | to last
34 26-Nov-2021 10:22 11 KB jmyers to previous | to last
33 26-Nov-2021 10:22 11 KB jmyers to previous | to last
32 26-Nov-2021 10:22 11 KB jmyers to previous | to last
31 26-Nov-2021 10:22 11 KB RForbes to previous | to last
30 26-Nov-2021 10:22 11 KB RForbes to previous | to last
29 26-Nov-2021 10:22 11 KB RForbes to previous | to last
28 26-Nov-2021 10:22 11 KB RForbes to previous | to last
27 26-Nov-2021 10:22 11 KB RForbes to previous | to last
26 26-Nov-2021 10:22 11 KB RForbes to previous | to last
25 26-Nov-2021 10:22 11 KB RForbes to previous | to last
24 26-Nov-2021 10:22 11 KB JMyers to previous | to last NAMING CONVENTION ==> NAMING CONVENTION AND STANDARDS
23 26-Nov-2021 10:22 11 KB RForbes to previous | to last
22 26-Nov-2021 10:22 10 KB RForbes to previous | to last
21 26-Nov-2021 10:22 10 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
ERD
ERD

Version management

Difference between version and

At line 75 added 3 lines
[{Image src='ERD_Dependent.JPG' width='350' align='center' link='attach/ERD/ERD_Dependent.JPG'}]
At line 76 removed one line
In this instance, the line starts as a single line at the Entity table and ends in many lines at the Unit table. This means that the entity may have many units associated with it, however, the unit cannot belong to more than one entity. Another way this can be expressed is that the Entity table is the PARENT of the Unit table and the Unit table is the DEPENDANT of the Entity table.
At line 78 changed one line
There can be a situation where two tables are parents to each other, which will be explained further on in this manual.
In this instance, the line starts as a single line at the Entity table and ends in many lines at the Unit table. This means that the entity may have many units associated with it, however, the unit cannot belong to more than one entity. Another way this can be expressed is that the Entity table is the PARENT of the Unit table and the Unit table is the DEPENDENT of the Entity table.
At line 82 added 10 lines
There can be a situation where two tables are parents to each other, which will be explained further on.
!Foreign Keys
Dependent tables will always have a [Foreign Key] that identifies its parent table.
The presence of the "many" branch (also known as crow's feet) indicates this foreign key.
For instance, within the Alias table, there will be a foreign key column (EID_ID) for the parent table, Identity.
Parent tables do not keep foreign keys and therefore their dependent tables can only be traced within the Oracle Data dictionary as referential constraints
At line 85 changed one line
*** PICTURE ***
[{Image src='ERD_Parent1.JPG' width='228' align='center' link='attach/ERD/ERD_Parent1.JPG'}]
At line 92 changed one line
*** PICTURE ***
[{Image src='ERD_Parent2.JPG' width='160' align='center' link='attach/ERD/ERD_Parent2.JPG'}]
At line 98 changed one line
***PICTURE ***
[{Image src='ERD_BoldLine.JPG' width='446' align='center' link='attach/ERD/ERD_BoldLine.JPG'}]
At line 103 changed one line
*** PICTURE ***
[{Image src='ERD_CurvedLine.JPG' width='306' align='center' link='attach/ERD/ERD_CurvedLine.JPG'}]
At line 122 changed 5 lines
*** PICTURE ***
This exclusive join means that the contact table may be tied to either the User table or the Identity table, but not both. These tables
cannot have the same contact.
Occasionally you will see an exclusive join that isn’t connected to multiple tables. This simply means that for brevity sake, not all dependant tables are displayed on the chart
*** PICTURE ***
[{Image src='ERD_ExclusiveJoin1.JPG' width='361' align='center' link='attach/ERD/ERD_ExclusiveJoin1.JPG'}]
This exclusive join means that the contact table may be tied to either the User table or the Identity table, but not both. These tables cannot have the same contact.
Occasionally you will see an exclusive join that isn’t connected to multiple tables. This simply means that for brevity sake, not all dependent tables are displayed on the chart
[{Image src='ERD_ExclusiveJoin2.JPG' width='272' align='center' link='attach/ERD/ERD_ExclusiveJoin2.JPG'}]
At line 132 changed one line
*** PICTURE ***
[{Image src='ERD_Transferable.JPG' width='323' align='center' link='attach/ERD/ERD_Transferable.JPG'}]
This page (revision-40) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop