# Register now to access 7 million high quality study materials (What's Course Hero?) Course Hero is the premier provider of high quality online educational resources. With millions of study documents, online tutors, digital flashcards and free courseware, Course Hero is helping students learn more efficiently and effectively. Whether you're interested in exploring new subjects or mastering key topics for your next exam, Course Hero has the tools you need to achieve your goals.

1 Page

### sql-airplane-example

Course: CS 460, Fall 2008
School: N. Michigan
Rating:

Word Count: 115

#### Document Preview

Show 1) all the airplanes and their prices. 2) Show all the airplanes and their seating capacity. 3) Show which tables exist. 4) Show the column definitions for the prices table. 5) Which airplane costs the most? 6) Which airplane has the fewest seats? 7) Which airplanes costs less than \$30,000. 8) Which airplanes do *not* cost between \$50,000 and \$5,000,000? 9) What is the ratio the of prices of the most...

Register Now

#### Unformatted Document Excerpt

Coursehero >> Michigan >> N. Michigan >> CS 460

Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

Course Hero has millions of student submitted documents similar to the one below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
Show 1) all the airplanes and their prices. 2) Show all the airplanes and their seating capacity. 3) Show which tables exist. 4) Show the column definitions for the prices table. 5) Which airplane costs the most? 6) Which airplane has the fewest seats? 7) Which airplanes costs less than \$30,000. 8) Which airplanes do *not* cost between \$50,000 and \$5,000,000? 9) What is the ratio the of prices of the most and least expensive airplane? 10) What is the cost per seat ratio for the airplanes? 11) Which airplane costs the most per seat? 12) Create a new table detailing airplanes and owners. Make something...

Textbooks related to the document above:
Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more. Course Hero has millions of course specific materials providing students with the best way to expand their education.

Below is a small sample set of documents:

N. Michigan - CS - 460
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;c36b54e66308f7af1aac9a33fa2258dad7cb25c1.txt&lt;/Key&gt;&lt;RequestId&gt;2FC3D90618102282&lt;/RequestId&gt;&lt;HostId&gt;zXYXxkirMeuRUast8LEhNvgwja0F
N. Michigan - CS - 460
DatingBrad Pitt - Jennifer AnistonJohn Mayer - Jenifer AnistonBrad Pitt - Angelina JolieJohn Mayer - Jessica SimpsonBen Aflec - Jennifer LopezBen Aflec - Jennifer GarnerPuff Daddy - Jennifer LopezNice or JerkBrad Pitt - NiceJohn Mayer - J
N. Michigan - CS - 228
Your mission is to write a server that prints the current date and time, and then one second later does it again, forever.It should handle mutliple clients. You must use fork().Every time a client connects, you should fork off a child to handle t
N. Michigan - CS - 228
Make a server for the chat client program.PointsFeature10The &quot;name&quot; command works. Every chatter's messages have a name associated with it.10The quit command works. When a person quits, a message is broadcast saying the person is logged o
N. Michigan - CS - 302
CS302 SUPPLEMENT UNIX SYSTEM ADMINISTRATIONDavid J. Powers 12-May-042nd Edition 2004Table of Contents1.0 Linux Installation (Redhat V9.0) 1.1 Image or Filesystem 1 1.2 Image or Filesystem 2 2.0 The Command Line and Shells 2.1 Introduction 2.2
UVA - P - 211
Brian Mercer3899500.0000001831933899000.00000027411487500.0000003899000.0000002473899500.000000Sub Area C Index11487500.000000
UVA - P - 211
Brian MercerSub Area C Index11487500.0000001831933899000.00000027411487500.0000003899000.000000247
UVA - P - 211
Brian Mercer 16011486500.000000Sub Area C Index11487000.000000165 166 176155170 169 178 185 175156 16211487500.00000015815011488000.0000003899500.000000181 182 197 218 195227 231 235201 206 205 209 211 214 217 222 229 226
UVA - P - 512
City of Charlottesville, VA - Skateboard Park PlanningJim Gould PLAN 512 GIS for Planning Fall 2007 Key Concepts &amp; GIS Terms: Spatial and Table Join, table editing, buffer, calculate The purpose of this project was to identify the most reasonable lo
N. Michigan - CS - 101
Make a web page saying something interesting on politics or history.It needs to include&lt;html&gt; &lt;body&gt;&lt;head&gt;&lt;a href=.&gt;&lt;p&gt;&lt;img src=.&gt;&lt;title&gt;&lt;b&gt;&lt;i&gt;&lt;font size=. color=.&gt;The page *must* be on the server.You get one point for every
N. Michigan - CS - 101
You shall write me a web site on Utopia. Your utopia must be better than* Sitting on a cloud singing Kumbaya.* Locked in a cave with Aristotle, Einstein, David Hasselhoff, and Pam Anderson* Strapped to a hospital bed with a cocaine drip into you
N. Michigan - CS - 101
Make me a three web pages about something you HATE. It should not be funny, but passionate.The first web page describes what it is you hate and why. It should include an unordered list of reasons to hate this thing. It should include at least th
N. Michigan - CS - 101
Your mission is to make a survey form. You want them to order some product.You get points for .* Using two textfields that have default values* Asking a password field* Using a select dropdowen menu* Providing radio buttons (at least two group
N. Michigan - CS - 101
Your mission is to make a teeter-totter computer.The user inputs 4 numbers. It tells if the teeter totter tilts left,tilts right, or is exactly balanced.1) How much does the kid on the left weigh2) How far from the middle is the kid on the lef
USC - CSCI - 577
f69af4dc13f91a6a7d5f9e8ff29d4bd0af2a4ba3.xls - Areas of Concern Log1) All steps in the Prototype Review are followed and completed fully 2) An objective for making the prototype in the first place 3) A description of the participants' participation
USC - CSCI - 577
Reviewed Document: LCP_F08a_T07_V1.0.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. Table of team personnel and roles is included in section 3.3. B) Technical Details a.
USC - CSCI - 577
Reviewed Document: LCP_F08a_T07_V1.0.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. Table of team personnel and roles is included in section 3.3. B) Technical Details a.
USC - CSCI - 577
Reviewed Document: FED_F08a_T07_V1.0.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. Well-formatted table of risks with current assessed values of loss, probability, and
USC - CSCI - 577
Reviewed Document: FED_F08a_T07_V1.0.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. Well-formatted table of risks with current assessed values of loss, probability, and
USC - CSCI - 577
4d7386763a7b98c20c021f24c73120170a610706.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: EZBayLCP v1.0 N/A ValuationReview # Revi
USC - CSCI - 577
LCP_VCP_AIR_IIVVb_F08a_T07_V1.0.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Kevin Stigerts Date Sent to Reviewer: Date Returned to
USC - CSCI - 577
Sheet1&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt; &lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;f9a561b837b0f52893737Page 1
USC - CSCI - 577
FED_VCP_AIR_IIVVb_F08a_T07_V1.0.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Kevin Stigerts Date Sent to Reviewer: Date Returned to
USC - CSCI - 577
1fe7a14ab81959d867d04311bf4c550f177c9c81.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Kevin StigertsEZBayUML v1.1 N/A Valuation
USC - CSCI - 577
Reviewed Document: UML_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. A Structure Diagram that shows the context in which the system is expected to operate (e.g. operational stakeholders, dev
USC - CSCI - 577
Reviewed Document: UML_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Provides initial system context, class diagrams, information elements and use case ov
USC - CSCI - 577
Reviewed Document: SSRD_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Most significant Project requirements, Interface requirements, Level of Service requirements 2. Capability requirements:
USC - CSCI - 577
Reviewed Document: SSAD_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. High-level definition of at least one feasible platform-independent architecture/design that includes: a. Definition of
USC - CSCI - 577
Reviewed Document: SSAD_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Attempts to provide architectural snapshot but fails to include all necessary diagra
USC - CSCI - 577
0e9e8e58f93d09ef88e136a711b766417e17f6a4.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Kevin StigertsEZBaySSAD v1.2 N/A Valuation
USC - CSCI - 577
Reviewed Document: SID_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Traceability matrix with latest information from WinWin Report, SSRD and OCD 2. Initial and other (if any) versions of pr
USC - CSCI - 577
Reviewed Document: SID_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Glossary b. Initial Traceability Table B) Technical Details a. None C) Major Errors &amp;
USC - CSCI - 577
Reviewed Document: OCD_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. System &amp; Operational Transformations b. Operational Capabilities c. Success Critical
USC - CSCI - 577
Reviewed Document: LCP_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Identification of team personnel and assigned roles 2. Update section 3.3 done in the VC Package if new required skills h
USC - CSCI - 577
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt; &lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;bd1d94fe8ff58c98b07a08675f05f8e7716b7c83.doc&lt;/Key&gt;&lt;RequestId&gt;8 1EAB3316EDAABED&lt;/RequestId&gt;&lt;HostId&gt;BAgH5AeDO3cX8F0N7FEzfFn9808
USC - CSCI - 577
Reviewed Document: UML_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. A Structure Diagram that shows the context in which the system is expected to operate (e.g. operational stakeholders, dev
USC - CSCI - 577
Reviewed Document: UML_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Provides initial system context, class diagrams, information elements and use case ov
USC - CSCI - 577
UML_DraftFC_AIR_IIVVb_F08a_T07_V1.1.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Date Sent to Reviewer: Reviewer: Review Leader email: Review Leader phone: Author: Kevin Stigerts 10/19/2008 Da
USC - CSCI - 577
Reviewed Document: SSRD_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Most significant Project requirements, Interface requirements, Level of Service requirements 2. Capability requirements:
USC - CSCI - 577
Reviewed Document: SSAD_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. High-level definition of at least one feasible platform-independent architecture/design that includes: a. Definition of
USC - CSCI - 577
Reviewed Document: SSAD_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Attempts to provide architectural snapshot but fails to include all necessary diagra
USC - CSCI - 577
Project Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author:SSAD_DraftFC_AIR_IIVVb_F08a_T07_V1.2.xls - Areas of Concern Log EZBaySSAD v1.2 N/A ValuationReview # Review Da
USC - CSCI - 577
Reviewed Document: SID_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Traceability matrix with latest information from WinWin Report, SSRD and OCD 2. Initial and other (if any) versions of pr
USC - CSCI - 577
Reviewed Document: SID_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Supplemental Review Report A) Management Overview a. Glossary b. Initial Traceability Table B) Technical Details a. None C) Major Errors &amp;
USC - CSCI - 577
Reviewed Document: OCD_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Exit Criteria 1. Shared vision and contexts for success-critical stakeholders 2. System transformation strategies: nominal, critical, and
USC - CSCI - 577
Reviewed Document: OCD_F08a_T07_V1.1.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 12, 2008 Supplemental Review Report A) Management Overview a. System &amp; Operational Transformations b. Operational Capabilities c. Success Critical
USC - CSCI - 577
Reviewed Document: LCP_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Identification of team personnel and assigned roles 2. Update section 3.3 done in the VC Package if new required skills h
USC - CSCI - 577
Reviewed Document: FED_F08a_T07_V1.2.doc Reviewer: Kevin Stigerts, Team 7 IIV&amp;V Date Reviewed: October 19, 2008 Exit Criteria 1. Identify key risks and their associated: a. Mitigation Plan(s) b. Probability c. Size of loss 2. Assurance that all major
N. Michigan - CS - 442
CS 442 - The Advanced Networking Final 1) How can a client tell if a server is uing select or poll on a file descriptor?2) It's very important to me that my server not crash. I anticipate a light load. What would be a better implementation techniqu
N. Michigan - CS - 442
CS 442 Advanced NetworkingIPv6 1. Under what circumstances would an IPv6 header be smaller than an IPv4 header?2. (Larger/Smaller) Right now a BGP routing table for IPv4 is many thousands of entries. If the Internet converted tomorrow to IPv6, wou
N. Michigan - CS - 442
1) What company in the lead developer for Rendezvous?2) Beyond attaching to a printer, name one example of Rendezvous I mentioned in class.3) What kind of packet does one send to test an IP address and see if it's in use. You can answer this with
USC - CSCI - 577
OCD_DraftFC_AIR_IIVVa_F08a_T07_V1.2 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:Ezbay- Team 7Operational Concept Description (OCD) ValuationReview # Review Date: Review Time:310/18/2008
USC - CSCI - 577
Life Cycle Plan (LCP)Version 1.0Life Cycle Plan (LCP)EZBay Team 7Prachi Pagey Ian Elston Snehal Vanjari Nupul Kukreja Alok Gurav Gabriel Alcocer Sagar Naware Kevin StigertsPlan and Control engineer Prototyper Requirements Engineer Software A
USC - CSCI - 577
SSAD_FCPackage_AIR_IIVVa_F08a_T07_V1.3 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:Ezbay- Team 7System and Software Architecture Description (SSAD) ValuationReview # Review Date: Review Time
USC - CSCI - 577
a9a20c8b4783ce8936e160d9df5cdfa302c1bc07.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Ezbay- Team 7Life Cycle Plan (LCP) Valuati
USC - CSCI - 577
c2a24bb37dfd4871873cb00c8c33557af7366df5.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: Ezbay- Team 7System and Software Requireme
USC - CSCI - 577
SSRD_FCPackage_AIR_IIVVa_F08a_T07_V1.2 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:Ezbay- Team 7System and Software Requirements Definition (SSRD) ValuationReview # Review Date: Review Time:
USC - CSCI - 577
Gabriel Alcocer CSCI 577a, Fall 2008Evaluation Report Life Cycle Plan (LCP)1) Management Overview This iteration of the Life Cycle Plan included a significant change that involved the addition of COCOMO II cost estimates. These estimates includ
USC - CSCI - 577
FED_FCPackage_AIR_IIVVa_F08a_T07_V1.3 - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:Ezbay- Team 7Feasability Evidence Description (FED) ValuationReview # Review Date: Review Time:111/1/200
USC - CSCI - 577
05049433bf99b8d93a5ce11940e35c309d67372c.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria: Reviewer: Review Leader email: Review Leader phone: Author: EZBayTP v1.0 N/A FoundationsReview # Rev
USC - CSCI - 577
TP_Draft_DC_AIR_IIVVb_F08a_T07_V1.0.xls - Areas of Concern LogProject Name: Artifact: Module: MBASE Phase/level: Activity: Exit Criteria:EZBayTP v1.0 N/A FoundationsReview # Review Date: Review Time:TP11/30/2008 1545hrs1bDate Sent to R