0% found this document useful (0 votes)

16 views27 pages

Lec03 SQL Basics

This document discusses multi-column primary keys and foreign keys in SQL by showing the syntax for declaring them. It also covers performing joins between multiple tables by linking columns and shows how to interpret the results of joins.

Uploaded by

Nguyễn Lê Huy Núp

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

16 views27 pages

Lec03 SQL Basics

Uploaded by

Nguyễn Lê Huy Núp

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 27

Introduction to Database Systems

Lecture 3: More SQL

(including most of Ch. 6.1-6.2)

1
Multi-column Keys
• This makes name a key:

CREATE TABLE Company(

name VARCHAR(20) PRIMARY KEY,
country VARCHAR(20),
employees INT,
for_profit BOOLEAN);

• How can we make a key on name & country?

2
Multi-column Keys
• Syntax change if a primary key has multiple columns:
goes away
CREATE TABLE Company(
name VARCHAR(20) PRIMARY KEY,
country VARCHAR(20),
employees INT,
added
for_profit BOOLEAN,
PRIMARY KEY (name, country));

3
Multi-column Keys (2)
• Likewise for secondary keys:
goes away
CREATE TABLE Company( name VARCHAR(20)
UNIQUE,
country VARCHAR(20),
employees INT,
added
for_profit BOOLEAN,
UNIQUE (name, country));

4
Multi-column Keys (3)
• This makes manufacturer a foreign key:

CREATE TABLE Product(

name VARCHAR(20),
good idea to include
price DECIMAL(10,2),
target column name
manufacturer VARCHAR(20)
REFERENCES Company(name));

5
Multi-column Keys (3)
• Similar syntax for foreign keys:

CREATE TABLE Product(

name VARCHAR(20),
price DECIMAL(10,2), now need both
name & country
manu_name VARCHAR(20),
manu_co VARCHAR(20), added
FOREIGN KEY (manu_name, manu_co)
REFERENCES Company(name, country));

6
One Way to Input Data
• Write a program that outputs SQL statements:
for (int a = 1; a <= 50; a++)
for (int b = 1; b <= 50; b++)
System.out.format(
“INSERT INTO T VALUES (%d,%d);\n“,
a, b);
• Feed those into SQLite:
sqlite3 foo.db < inputs.sql

7
Demo: MakeTriples.java

8
Warning
• Be very careful when doing this with strings:
System.out.format(
”INSERT INTO T2 VALUES (%d, ‘%s’);”,
3, ”O’Shaughnessy”);

Becomes:
INSERT INTO T2 VALUES (3, ‘O’Shaughnessy’);
which is a syntax error in this case

9
https://xkcd.com/327/

10
Warning (cont)
• Be very careful when doing this with strings:
System.out.format(
”INSERT INTO T VALUES (%d, ‘%s’);”,
3, ”O’Shaughnessy”);
• This allows a SQL injection attack!
– Must check for quotes and escape (or disallow) them.
– We’ll see safer ways to do this using JDBC

• DBMSs usually have faster ways to input data

– SQLite has .import (try with .mode csv)
11
SQLite Uses
• SQLite is just a library

• Can be used as part of any C/C++/Java program

– ex: could be used in an iPhone app

• Can be used in Chrome & Safari

– no support in Firefox or IE

12
Demo: websql.html in Chrome
(Note: this HTML/JS code is out of class scope)

Also selection & projection examples

(see lec03-sql-basics.sql)

13
Physical Data Independence
• SQL doesn’t specify how data is stored on disk

• No need to think about encodings of data types

– ex: DECIMAL(10,2)
– ex: VARCHAR(255)
• does this need to use 255 bytes to store ‘hello’?

• No need to think about how tuples are arranged

– ex: could be row- or column-major ordered
– (Most DBMSs are row-ordered, but Google’s BigQuery is
column-oriented.)
14
SQLite Gotchas
• Allows NULL keys
– At most one tuple can have NULL in the key
– According to the SQL standard, PRIMARY KEY should
always imply NOT NULL, but this is not the case in SQLite

• Does not support boolean or date/time columns

• Doesn’t always enforce domain constraints!
– will let you insert a string where an INT is expected

• Doesn’t enforce foreign key constraints by default

• Etc…
15
DISTINCT and ORDER BY
• Query results do not have to be relations
– i.e., they can have duplicate rows
– remove them using DISTINCT

• Result order is normally unspecified

– choose an order using ORDER BY
– e.g., ORDER BY country, cname
– e.g., ORDER BY price ASC, pname DESC

• Examples in lec03-sql-basics.sql
16
Joins
• Can use data from multiple tables:
SELECT pname, price
FROM Product, Company
WHERE manufacturer = cname AND
country = ‘Japan’ AND
price < 150;

• This is a selection and projection of the “join” of the

Product and Company relations.

17
Interpreting Joins
• A JOIN B produces one row for every pair of rows
– one row from A and one row from B