Create PostgreSQL Schema Lab2

Original price was: $35.00.Current price is: $30.00.

Rate this product

Lab Assignment 2 CMPS 180
2 Goal
The goal of the second assignment is to create a PostgreSQL data schema with 5 tables that are very
similar to the tables that you created in Lab1. The tables have the same names, attributes and data
types as the tables of Lab1, and the same primary keys but there are some UNIQUE constraints and
some restrictions on NULLs.
After you create the data schema with the 5 tables, you will be required to write some SQL statements
that use those tables. Under Resources→Lab2, we’ve provided you with data that you can load into
your tables so that you can test the results of your queries. Testing can prove that a query is wrong, but
not that it is right, so be careful.
Lab2 is due in two weeks, so you will have an opportunity to discuss the assignment during the
Discussion Section in the first week of the assignment, and to discuss issues you have had in writing a
solution to the assignment during the Discussion Section of the second week. Instructions for
submitting the assignment appear at the end of this document.
3 Lab2 Description
3.1 Create PostgreSQL Schema Lab2
You will create a Lab2 schema to set apart the database tables created in this lab from ones you will
create in future, as well as from tables (and other objects) in the default (public) schema. Note that the
meaning of schema here is specific to PostgreSQL and different from the general meaning. See here for
more details on PostgreSQL schemas. You create the Lab2 schema like this:
Now that you have created the schema, you want to set Lab2 to be your default schema when you use
psql. If you do not set Lab2 as the default schema, then you will have to qualify your table names with
the schema name (e.g. Lab2.Customers). To set the default schema, you modify your search path. (For
more details, see here.)
You will need to log out and log back in to the server for this default schema change to take effect.
(Students often forget to do this.)
You do not have to include the CREATE SCHEMA or ALTER ROLE statements in your solution.
Lab Assignment 2 CMPS 180 – Winter 2019 Due: Wednesday, Feb 6, 11:59pm
Page 2 of 5
3.2 Create tables
You will create tables in schema Lab2 for the tables Exchanges, Stocks, Customers, Trades and Quotes.
The attributes of the 5 tables are the same as the tables of Lab1. Data types for the attribute names in
these tables are also the same as the ones specified for the tables of Lab1. The Primary Keys are also
the same. However, the tables must have the additional constraints described in the next section.
3.2.1 Constraints
The following attributes cannot be NULL. All other attributes can be (but remember that attributes in
Primary Keys also cannot be NULL).
• In Stocks: stockName
• In Trades: price
• In Trades: volume
Also, the following must be unique for the specified table. That is, there cannot be identical rows in that
table that have exactly the same (non-NULL) values for all of those attributes (composite unique
• In Exchanges: the attribute exchangeName
• In Stocks: the attribute stockName
• In Customers: the 2 attributes custName and address
For example, the third constraint says that there can’t be two rows in Customers that have the same
values for both custName and address (if both custName and address are not NULL). Think of this as
saying that there can’t be two different customers who have both the same custName and the same
You will write a CREATE TABLE command for each of the 5 tables. Save the commands in the file
Lab Assignment 2 CMPS 180 – Winter 2019 Due: Wednesday, Feb 6, 11:59pm
Page 3 of 5
4 SQL Queries
Below are English descriptions of the five SQL queries that you need to write for this assignment, which
you will include in files queryX.sql, where X is the number of the query, e.g., your SQL statement for
Query 1 will be in the file query1.sql, and so forth. Follow the directions as given. You will lose points
if you give extra tuples or attributes in your results, if you give attributes in with the wrong names or in
the wrong order, or if you have missing or wrong results. You will also lose points if your queries are
unnecessarily complex, even if they are correct.
Terminology: A customer is someone who appears as a row in Customer, a stock appears as a row in
Stocks, a trade appears as a row in Trades, etc. The name of a customer is given by custName, and the
name of a stock is given by stockName, etc. If (‘NYSE’, ‘ORCL’, ‘Oracle’, ‘500 Oracle Parkway. Redwood
Shores CA’) is a row in Stocks, and the exchangeName in Exchanges that has exchangeID ‘NYSE’ is
‘New York Stock Exchange’, then we say that Oracle is listed on the ‘New York Stock Exchange’.
4.1 Query 1
A customer is valid if isValidCustomer is true for that customer. Find the customerID, custName and
address for each valid customer whose name has the string ‘FAKE’ (all capitals) appearing anywhere in
their name. No duplicates should appear in your result.
4.2 Query 2
Find the name and symbol for each stock that is not listed on the ‘NASDAQ Stock Exchange’. The
attributes in your result should appear as name and symbol. No duplicates should appear in your result.
4.3 Query 3
Output the exchangeID and stockName of each stock for which there is at least one quote whose price is
less than 314.15. No duplicates should appear in your result.
4.4 Query 4
The cost for a trade is price * volume for that trade. For each trade in which
a) the cost is greater than or equal to five thousand,
b) the buyer is a valid customer, and
c) the buyer’s category isn’t NULL,
output the exchangeID, symbol, buyerID, cost, and the category of the buyer. The attribute for the cost of
the trade should appear as theCost in your result. No duplicates should appear in your result.
4.5 Query 5
Output the names of the buyers and sellers of stocks that were traded (that is, for which there was a
trade) that occurred before ‘2018-01-01 12:00:00’. Your result should have attributes exchangeID,
stockName, buyerName, and sellerName. No duplicates should appear in your result.
Lab Assignment 2 CMPS 180 – Winter 2019 Due: Wednesday, Feb 6, 11:59pm
Page 4 of 5
5 Testing
While your solution is still a work in progress, it is a good idea to drop all objects from the database
every time you run the script, so you can start fresh. Of course, dropping each object may be tedious,
and sometimes there may be a particular order in which objects must be dropped. The following
commands (which you can put at the top of create.sql if you want, but you don’t have to), will drop your
Lab2 schema (and all objects within it), and then create the (empty) schema again:
Before you submit, login to your database via psql and execute your script. As you’ve learned already,
the command to execute a script is: \i <filename>.
Under Resources→Lab2 on Piazza, we have provided a load script named lab2_data_loading.sql that
loads data into the 5 tables of the database. You can execute that script with the command:
\i lab2_data_loading.sql.
You can test your 5 queries using that data, but you will have to figure out on your own whether your
query results are correct. We won’t provide answers, and students should not share answers with
other students. Also, your queries must be correct on any database instance, not just on the data that
we provide. You may want to test your SQL statements on your own data as well.
Lab Assignment 2 CMPS 180 – Winter 2019 Due: Wednesday, Feb 6, 11:59pm
Page 5 of 5
6 Submitting
1. Save your scripts for table creations and query statements as create.sql and query1.sql through
query5.sql You may add informative comments inside your scripts if you want (the server
interprets lines that start with two hyphens as comment lines).
2. Zip the file(s) to a single file with name where XXXXXXX is your 7-digit
student ID. For example, if a student’s ID is 1234567, then the file that this student submits for
Lab2 should be named
To generate the zip file you can use the Unix command:
zip Lab2_1234567 create.sql query1.sql query2.sql query3.sql query4.sql query5.sql
(Of course, you use your own student ID, not 1234567.)
3. You should already know how to transfer the files from the UNIX timeshare to your local machine
before submitting to Canvas. If you are still not familiar with the process, use the instructions we
provided at the Lab1 assignment.
4. Lab2 is due by 11:59pm on Wednesday, February 6. Late submissions will not be accepted, and
there will be no make-up Lab assignments.
5. You may lose credit if your queries are unnecessarily complex, even if they are correct. For
example, if you use DISTINCT but it’s not needed, you might lose half a point. Of course, you will
also lose credit if DISTINCT is needed and you omit it.
6. Be sure to follow directions about Academic Integrity that are in the Syllabus and Lecture1. If
you have any questions about those directions, please speak to the instructor as soon as possible.


There are no reviews yet.

Be the first to review “Create PostgreSQL Schema Lab2”

Your email address will not be published. Required fields are marked *

Scroll to Top