Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Functional dependency
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Employee department === A classic example of functional dependency is the employee department model. {| class="wikitable" |- ! Employee ID !! Employee name !! Department ID !! Department name |- | 0001 || John Doe || 1 || Human Resources |- | 0002 || Jane Doe || 2 || Marketing |- | 0003 || John Smith || 1 || Human Resources |- | 0004 || Jane Goodall || 3 || Sales |} This case represents an example where multiple functional dependencies are embedded in a single representation of data. Note that because an employee can only be a member of one department, the unique ID of that employee determines the department. * Employee ID β Employee Name * Employee ID β Department ID In addition to this relationship, the table also has a functional dependency through a non-key attribute * Department ID β Department Name This example demonstrates that even though there exists a FD Employee ID β Department ID - the employee ID would not be a logical key for determination of the department Name. The process of normalization of the data would recognize all FDs and allow the designer to construct tables and relationships that are more logical based on the data.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)