Exercise 6.1 - Transactions:

In pg-admin, create a SQL script that does the following:

Tables:

• Customers. Alias as cu
• Sales_Header. Alias as sh
• Sales_Detail. Alias as sd

Attributes:

• sale_id. Alias as Transaction
• customer_name. Alias as Customer
• date_sale. Alias as Date
• feedback_score. Alias as Feedback
• The total revenue for this transaction. Alias as Amount
• The total number of items_sold. Alias as Items

Other considerations:

• Order by date_sale with the most recent date first
• Limit the output to the first 10 rows only

• Test this script in PostgreSQL

  • The names and data should match the screenshot

• Convert this SQL script into a VIEW called v_Top_Transactions

• Append SQL to SELECT * FROM this VIEW into the space provided in line 13 of backend/routes/transactions.js

• Save and close backend/routes/transactions.js

• In a new browser tab, preview the transactions route (http://localhost:5001/transactions)
  • This should be populated with an array of 10 objects for each transaction

• This is the data that our front-end will use to populate the Transactions table on the web page

• In the main Sequel-Mark website (http://localhost:5001), check the Transactions table has been populated