- Relational Databases
- Writing Basic SQL Queries
- Writing Basic Queries using Knex.js
Your assignment page on Canvas should contain instructions for submitting this project. If you are still unsure, reach out to School Staff.
Visit SQL Try Editor at W3Schools.com using Chrome and build the queries below. Once they work copy them to the queries.sql
file at the root of the project.
- Find all customers with postal code 1010. Returns 3 records.
- Find the phone number for the supplier with the id 11. Should be (010) 9984510.
- List first 10 orders placed, sorted descending by the order date. The order with date 1997-02-12 should be at the top.
- Find all customers that live in London, Madrid, or Brazil. Returns 18 records.
- Add a customer record for "The Shire", the contact name is "Bilbo Baggins" the address is "1 Hobbit-Hole" in "Bag End", postal code "111" and the country is "Middle Earth".
- Update Bilbo Baggins record so that the postal code changes to "11122".
Clicking the Restore Database
button in the page will repopulate the database with the original data and discard all changes you have made.
We have provided some records inside the "accounts" table of the budget.db3
database. You can restore the database (even after deleting the database) by running the following command:
npm run resetdb
field | data type | metadata |
---|---|---|
id | unsigned integer | primary key, auto-increments, generated by database |
name | string | required, unique |
budget | numeric | required |
-
Write the following db access functions inside
api/accounts/accounts-model.js
using Knex:getAll
resolves to an array of accounts (or an empty array)getById
resolves to an account by the given idcreate
resolves to the newly created accountupdateById
resolves to the updated accountdeleteById
resolves to the deleted account
-
Here is a cheatsheet for working with SQLite with Knex:
db("foo-table"); // returns a promise that resolves to an **array** with all records in the table
db("foo-table").where({ role: "Student", active: true }); // resolves to an **array** of all records that satisfy the where
db("foo-table").where("name", "Mary"); // is an alternative for when there is just one where condition
db("foo-table").where("id", 7).first(); // will resolve to the **record** we want (if the id is unique for a table) or undefined
db("foo-table").insert({ bar: "baz" }); // resolves to an **array** containing the **ids of the records** inserted into the table
db("foo-table").where("id", id).update({ bar: "new bar" }); // resolves to the **number of records** affected by the update
db("foo-table").where("id", id).delete(); // resolves to the **number of records** affected by the delete
-
Write the following middlewares inside
api/accounts/accounts-middleware.js
:-
checkAccountPayload
returns a status 400 with ifreq.body
is invalid:- If budget is not able to be converted into a number, return `{ message: "budget of account must be a number" }` - If budget is a negative number or over one million, return `{ message: "budget of account is too large or too small" }`
-
checkAccountId
returns a status 404 with a{ message: "account not found" }
ifreq.params.id
does not exist in the database -
checkAccountNameUnique
returns a status 400 with a{ message: "that name is taken" }
if the trimmedreq.body.name
already exists in the database
-
-
Write CRUD for the
accounts
resource, using the middlewares and model functions above wherever appropriate:[GET] /api/accounts
returns an array of accounts (or an empty array if there aren't any).[GET] /api/accounts/:id
returns an account by the given id.[POST] /api/accounts
returns the created account. Leading or trailing whitespace on budgetname
should be trimmed before saving to db.[PUT] /api/accounts/:id
returns the updated account. Leading or trailing whitespace on budgetname
should be trimmed before saving to db.[DELETE] /api/accounts/:id
returns the deleted account.
-
Manually test your endpoints with a REST client like
Insomnia
orPostman
to check they are working as expected. -
Test your endpoints automatically by running
npm test
.
- You are welcome to create additional files but do not move or rename existing files or folders.
- Do not alter your
package.json
file except to install additional libraries or add additional scripts. - In your solution, it is essential that you follow best practices and produce clean and professional results.
- Schedule time to review, refine, and assess your work.
- Perform basic professional polishing including spell-checking and grammar-checking on your work.
The following exercises require research, the concepts needed to complete them have not been covered in class yet.
-
Run more queries.
- Find a query to discover how many different cities are stored in the Customers table. Repeats should not be double counted. Should be 69.
- Find all suppliers who have names longer than 20 characters. Returns 11 records.
- Add a
query string
option to theGET /api/accounts
endpoint. Thequery string
may containlimit
,sortby
andsortdir
keys. If these keys are provided, use these values to limit and sort theaccounts
which are selected from the database. Reference the docs for sorting and limiting in knexjs.org.
// sample req.query object { limit: 5, sortby: 'id', sortdir: 'desc' }