The Driver Relationship team wants to analyze drivers and their car usages in InstantRide for the month October. Thus, they want to focus on each driver and respective car allocation occurred. In more detail, the team requires the DRIVER_ID and the CAR_ID with their usage counts as the TOTAL column for the travels occurred in the month of October. Since the team wants to also learn the total number of the travels by the drivers you need to use GROUP BY ROLLUP functionality

Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
icon
Related questions
Question

The Driver Relationship team wants to analyze drivers and their car usages in InstantRide for the month October. Thus, they want to focus on each driver and respective car allocation occurred. In more detail, the team requires the DRIVER_ID and the CAR_ID with their usage counts as the TOTAL column for the travels occurred in the month of October. Since the team wants to also learn the total number of the travels by the drivers you need to use GROUP BY ROLLUP functionality.

The image displays a table titled "TRAVELS Table." This table contains detailed information about various travel instances, with each row representing a unique travel record. Below is a detailed transcription of each column in the table:

1. **TRAVEL_ID**: Unique identifier for each travel record.
   - Examples: 5001, 5002, 5003, etc.

2. **TRAVEL_START_TIME**: The start date and time of the travel in the format YYYY-MM-DD HH:MM:SS.
   - Examples: 2019-10-01 04:04:55, 2019-10-01 05:57:33, etc.

3. **TRAVEL_END_TIME**: The end date and time of the travel, also in the format YYYY-MM-DD HH:MM:SS.
   - Examples: 2019-10-01 04:14:19, 2019-10-01 06:12:33, etc.

4. **TRAVEL_START_LOCATION**: The starting address of the travel.
   - Examples: 9614 Vox Road, 47 Church Street, 2 Windsor Road, etc.

5. **TRAVEL_END_LOCATION**: The ending address of the travel.
   - Examples: 84 Church Lane, 68 High Street, 95 West Street, etc.

6. **TRAVEL_PRICE**: The price of the travel in monetary units.
   - Examples: 15.44, 20.56, 12.32, etc.

7. **DRIVER_ID**: Unique identifier for the driver associated with each travel record.
   - Examples: 2001, 2002, 2003, etc.

8. **CAR_ID**: Unique identifier for the car used for each travel record.
   - Examples: 1003, 1001, 1002, etc.

9. **USER_ID**: Unique identifier for the user or passenger for each travel record.
   - Examples: 3005, 3003, 3007, etc.

10. **TRAVEL_DISCOUNT**: Any discount applied to the travel price, displayed in decimal form. Null values indicate no discount.
    - Examples: NULL, 0.10, 0.13, etc.

The table provides an organized structure for analyzing travel data, focusing on key aspects like timings, locations, pricing, and involved parties.
Transcribed Image Text:The image displays a table titled "TRAVELS Table." This table contains detailed information about various travel instances, with each row representing a unique travel record. Below is a detailed transcription of each column in the table: 1. **TRAVEL_ID**: Unique identifier for each travel record. - Examples: 5001, 5002, 5003, etc. 2. **TRAVEL_START_TIME**: The start date and time of the travel in the format YYYY-MM-DD HH:MM:SS. - Examples: 2019-10-01 04:04:55, 2019-10-01 05:57:33, etc. 3. **TRAVEL_END_TIME**: The end date and time of the travel, also in the format YYYY-MM-DD HH:MM:SS. - Examples: 2019-10-01 04:14:19, 2019-10-01 06:12:33, etc. 4. **TRAVEL_START_LOCATION**: The starting address of the travel. - Examples: 9614 Vox Road, 47 Church Street, 2 Windsor Road, etc. 5. **TRAVEL_END_LOCATION**: The ending address of the travel. - Examples: 84 Church Lane, 68 High Street, 95 West Street, etc. 6. **TRAVEL_PRICE**: The price of the travel in monetary units. - Examples: 15.44, 20.56, 12.32, etc. 7. **DRIVER_ID**: Unique identifier for the driver associated with each travel record. - Examples: 2001, 2002, 2003, etc. 8. **CAR_ID**: Unique identifier for the car used for each travel record. - Examples: 1003, 1001, 1002, etc. 9. **USER_ID**: Unique identifier for the user or passenger for each travel record. - Examples: 3005, 3003, 3007, etc. 10. **TRAVEL_DISCOUNT**: Any discount applied to the travel price, displayed in decimal form. Null values indicate no discount. - Examples: NULL, 0.10, 0.13, etc. The table provides an organized structure for analyzing travel data, focusing on key aspects like timings, locations, pricing, and involved parties.
In the **USERS** table, information for the users is stored with their first name, last name, and email:

| USER_ID | USER_FIRST_NAME | USER_LAST_NAME | USER_EMAIL           |
|---------|-----------------|----------------|----------------------|
| 3001    | Jack            | Hill           | j.hill@email.com     |
| 3002    | Ryan            | Collins        | r.collins@xmail.com  |
| 3003    | Nursin          | Yilmaz         | n.atak@gmail.com     |
| 3004    | Sarah           | Price          | s.price@xmail.com    |
| 3005    | Bobby           | Griffin        | b.griffin@xmail.com  |
| 3006    | Randy           | Clark          | r.clark@xmail.com    |
| 3007    | Jose            | Thomas         | j.thomas@xmail.com   |
| 3008    | Nursin          | Yilmaz         | n.yilmaz@email.com   |

**USERS Table**

In the **DRIVERS** table, all the drivers in the InstantRide are stored with their name, driving license number and check and rating information:

| DRIVER_ID | DRIVER_FIRST_NAME | DRIVER_LAST_NAME | DRIVER_DRIVING_LICENSE_ID | DRIVER_START_DATE | DRIVER_DRIVING_LICENSE_CHECKED | DRIVER_RATING |
|-----------|-------------------|------------------|---------------------------|------------------|-------------------------------|--------------|
| 2001      | Willie            | Butler           | 1874501                   | 2019-09-12       | 1                             | 4.4          |
| 2002      | Justin            | Howard           | 1953383                   | 2019-09-09       | 1                             | 4.8          |
| 2003      | Anthony           | Walker           | 1735487                   | 2019-09-15       | 1                             | 3.5          |
| 2004      | Ece               | Yilmaz           | 1734747                   | 2019-08-15       | 1                             | 0            |

**DRIVERS Table**

In the **CARS** table, all the cars in the InstantRide system are kept with the license plate, model and year:

| CAR_ID | CAR_PLATE  |
Transcribed Image Text:In the **USERS** table, information for the users is stored with their first name, last name, and email: | USER_ID | USER_FIRST_NAME | USER_LAST_NAME | USER_EMAIL | |---------|-----------------|----------------|----------------------| | 3001 | Jack | Hill | j.hill@email.com | | 3002 | Ryan | Collins | r.collins@xmail.com | | 3003 | Nursin | Yilmaz | n.atak@gmail.com | | 3004 | Sarah | Price | s.price@xmail.com | | 3005 | Bobby | Griffin | b.griffin@xmail.com | | 3006 | Randy | Clark | r.clark@xmail.com | | 3007 | Jose | Thomas | j.thomas@xmail.com | | 3008 | Nursin | Yilmaz | n.yilmaz@email.com | **USERS Table** In the **DRIVERS** table, all the drivers in the InstantRide are stored with their name, driving license number and check and rating information: | DRIVER_ID | DRIVER_FIRST_NAME | DRIVER_LAST_NAME | DRIVER_DRIVING_LICENSE_ID | DRIVER_START_DATE | DRIVER_DRIVING_LICENSE_CHECKED | DRIVER_RATING | |-----------|-------------------|------------------|---------------------------|------------------|-------------------------------|--------------| | 2001 | Willie | Butler | 1874501 | 2019-09-12 | 1 | 4.4 | | 2002 | Justin | Howard | 1953383 | 2019-09-09 | 1 | 4.8 | | 2003 | Anthony | Walker | 1735487 | 2019-09-15 | 1 | 3.5 | | 2004 | Ece | Yilmaz | 1734747 | 2019-08-15 | 1 | 0 | **DRIVERS Table** In the **CARS** table, all the cars in the InstantRide system are kept with the license plate, model and year: | CAR_ID | CAR_PLATE |
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps

Blurred answer
Knowledge Booster
Intermediate SQL concepts
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
Recommended textbooks for you
Database System Concepts
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education