orders, order_details and customers. The orders table contains basic information about each order, including the order ID and customer ID, customers table contains information about customer, while the order_details table contains the details of each order, including the product ID, quantity, and price. You want to create a view that shows the order ID, customer name, product name, quantity, and price for all orders.
Example of the orders table:
| order_id | customer_id | order_date |
|---|---|---|
| 1 | 1 | 2022-03-01 |
| 2 | 2 | 2022-03-02 |
| 3 | 1 | 2022-03-03 |
| 4 | 3 | 2022-03-04 |
Example of the order_details table:
| order_id | product_id | quantity | price |
|---|---|---|---|
| 1 | 1 | 3 | 10.00 |
| 2 | 2 | 5 | 15.00 |
| 1 | 3 | 2 | 20.00 |
| 4 | 1 | 1 | 8.50 |
Example of the customers table:
| customer_id | customer_name | city |
|---|---|---|
| 1 | Laurence Lebihan | London |
| 2 | Diego Roel | Madrid |
Which of the following CREATE VIEW statements would accomplish this?
orders and products. You want to create a view that shows the order ID, product name, and quantity for all orders that include a particular product. Which of the following CREATE VIEW statements would accomplish this?Table Example:orders table:| order_id | product_id | quantity |
|----------|------------|----------|
| 1 | 1 | 3 |
| 2 | 2 | 5 |
| 3 | 1 | 2 |
| 4 | 3 | 1 |
products table:
| id | product_name |
|----|--------------|
| 1 | Widget A |
| 2 | Widget B |
| 3 | Widget C |
What is the difference between a regular view and a materialized view in PostgreSQL?
Which of the following cannot be stored in a relational database easily?
Which database feature ensures data is stored consistently (e.g., all customer emails follow the same format)?
What is a common advantage of relational databases?
What is the benefit of using materialized (indexed) views?
Which type of view combines data from one or more base tables (or views) into a new virtual table?