100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
Previously searched by you
Summary TermProject.docx INFO321 PROJECT PAPER American Public University INFO321 1. We can see that the table presents a one to many relationships because a pilot can only work for one airline while the airline can have many pilots also, this can t be the $7.49
Add to cart
Summary TermProject.docx INFO321 PROJECT PAPER American Public University INFO321 1. We can see that the table presents a one to many relationships because a pilot can only work for one airline while the airline can have many pilots also, this can t be the
2 views 0 purchase
Course
Csu
Institution
Columbia Southern University
TermP INFO321 PROJECT PAPER American Public University INFO321 1. We can see that the table presents a one to many relationships because a pilot can only work for one airline while the airline can have many pilots also, this can t be the other way around. In fact, the pilot entity represents ...
termprojectdocx info321 project paper american public university info321 1 we can see that the table presents a one to many relationships because a pilot can only work for one airline while th
Written for
Columbia Southern University
Csu
All documents for this subject (454)
Seller
Follow
helperatsof1
Reviews received
Content preview
INFO321
PROJECT PAPER American
Public University INFO321
1. We can see that the table presents a one to many relationships because a pilot can only
work for one airline while the airline can have many pilots also, this can’t be the other
way around. In fact, the pilot entity represents the attributes of PilotID, FName, LName,
JobTitle, Salary and AirlineID. A A pilot can have any PilotID as long as the ID does
not replicate itself. The PilotID is the primary key. The Airlines entity, on the other
hand, represent the AirlineID, NPLanes, NRoutes, NPilots. The Airlines entity is
dependent on the Pilot entity hence the AirlineID appears as a foreign key (FK) on the
Pilot entity.
2. Functional dependency is a constraint between two sets of attributes in a table from a
database. It mainly includes a primary key (PK) and any other non-key attributes in the
table. From the report, the PilotID attribute is a functional decency which uniquely
identifies the FName, LName, JobTitle and Salary since with just the pilot ID one can
obtain the first name, last name, job tittle and salary of a pilot.
3. From the table PilotID is only represented by one AirlineID, meanwhile more than one
AirlineID represent more than one PilotID. So, the relationship between the pilot and the
Airline entity is a one-to-many relationship because a pilot can only work for a single
airline, but an airline can have several pilots.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller helperatsof1. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $7.49. You're not tied to anything after your purchase.