Information Technology: Database concepts and applications The Everest Books dat
ID: 3790655 • Letter: I
Question
Information Technology: Database concepts and applications
The Everest Books database has four tables i e., books, customers, orderinfo, and orders everest Tables books customers orderinfo orders The columns of each table are shown below. Also there are some example recorders in each of these tables, which are displayed in MySQL Workbench (table boo 1 SELECT FROM everest.books 1 SELECT FROM everest. customers Result Grid t* Filter Rows: I Result Grid Filter Rows Edit: Export ISBN Title UnitPrice Id Name Company Street City State zip 0439357624 Born Confused 16.95 25 Scenic Road Hilltop NJ 18901 1 Jones, Tom Acrme 0670031844 White Mughal 34.95 NULL 2 Wise, Susan 32 New Road Union AZ 78901 0929306260 Java 49.95 3 Singh, Liza FastTrack 155 Route 133 Holmdel FL 48901 0929306279 Bell Labs 29.95 SELECT FROM everest orderinfo 1 SELECT FROM everest. orders; tA Filter Rows: Result Grid Order Id ISBN Qty UnitPrice Filter Rows 0929306279 29.95 Result Grid Edit: 0929306260 1 49.95 Id CustomerId Order Date shipDate shipping 0439357624 16.95 2004-03-31 2004-03-31 4.99 0670031844 1 34.95 2004-04-01 2004-04-02 5.99 0929306279 1 29.95 49.95 2004-04-01 2004-04-02 3.99 0929306260 1 0439357624 16.95 2004-04-02 2004-04-02 6.99 0670031844 1 34.95Explanation / Answer
The individual Book price will remain the price applying at Order_Info and not change subsequently.
The order Table should contain the UnIt Price because , it may happen that the price of book might change later
You can't later refer back to the Books table for unit price since, they got changed based on dicounts or change in price.
So its good to keep the unit price i.r the price on which we sold this book and not refer or go back to books table to see its price [We never know it might got changed or its the discounted price ]
Thanks, let me know if there is any concern.