WELCOME TO CFG

YOUR INTRODUCTION TO
DATABASES & SQL PROGRAMMING LANGUAGE

TECH OPENS UP LIMITLESS OPPORTUNITIES FOR GIRLS

 R SE Y
O U NE
C UR
JO

SESSION 7 SESSION 8
Database design Project
and data presentations
visualisation

SESSION 6
Data management
using SQL coding
techniques
SESSION 5 SESSION 4
Data manipulation Data analysis for
with SQL complex structures
programming
language

SESSION 3

Data analysis

SESSION 1 SESSION
MODULE 22
Introduction to SQL SQL coding and
programming Database
language and Data management
Science technique
 SQL CODING
DB MANAGEMENT
TECHNIQUE
MODULE 1: HTML

1. DB design and management:

• Normalisation
• Constraints on a table
• Primary and Foreign keys
• Index

2. SQL Coding:
• Data Modification Techniques
• Data Retrieval Techniques (SELECT statements)
02
 PART 1:
DB DESIGN AND
MANAGEMENT
 • The idea behind normalisation is to organise a database into tables in such way
that a table is created about one specific topic only.

• The main reasons to normalise a database are:

• to minimise duplicated data,
• to minimize or avoid data modification issues
• to simplify queries
DATABASE
NORMALISATION • There are three common forms of database normalization:
• 1st, 2nd, and 3rd normal form or
• 1NF, 2NF, and 3NF respectively

NB please read about 3 forms of normalisation:

https://www.complexsql.com/database-normalization/
 • We want to design our DB that it can answer as many ‘questions’ as possible including the
ones we may ask in the future. We want to design it in a way that we can always add more
data to it and easily modify existing data if necessary.

Table 1 – NO normalisation applied

Employee No Employee Name Department

1 Mary FINANCE,TAX

2 Edith HR
NORMALISATION
EXAMPLE 1 3 Anna ADMIN

Table 2.1 – normalised Table 2.2 – normalised

Employee No Employee Name Employee No Department

1 Mary 1 FINANCE

2 Edith 1 TAX

3 Anna 2 HR

3 ADMIN
NORMALISATION
EXAMPLE 2

source: http://salinaitmind.blogspot.com/2012/10/data-warehouse-data-normalization.html
 Normalisation
“…make sure that every attribute is single valued and provides a fact completely
and only about its primary key”

• Single Valued
• The attribute can only contain one piece of information
• E.g. Polly, Moore should be two attributes – first name and surname

• Provides a fact completely

• A given Primary Key should only return no more than one of every attribute
• E.g. ID1 (the PK) should only return one row

• Only about its primary key

• Each attribute must provide a fact about the PK and nothing else.
• E.g. if we have a field that tells us when the room was last booked, and a flag stating when this was last
booked, it becomes redundant
 First Normal Form (1NF)
Each attribute contains only one value and cannot be broken down into anything
smaller

Name Address

Polly Moore 123 Corn Street, Bristol, BS1 6EB

Chloe Moore 1 Kilmarnock Street, Glasgow, GL1 6BE

First Name Surname Number Street City Postcode

Polly Moore 123 Corn St Bristol BS1 6EB

Chloe Moore 1 Kilmarnock St Glasgow GL1 6BE

 Second Normal Form (2NF)
Cannot contain any partial Dependencies

ID First Name Surname Course Course Cost

1 Polly Moore Data Science £100

2 Chloe Moore Data Engineering £240

3 Polly Moore Data Engineering £240

CourseID Course Cost ID Forename Surname Course

1 Data Science £100 1 Polly Moore 2
2 Data £200 2 Chloe Moore 2
Engineering
3 Polly Moore 1
Third Normal Form (3NF)

All Non-Primary Fields are dependent on the Primary Key

ID Forename Surname Subject Location Country

1 Polly Moore Data Engineering Bristol England

2 Chloe Moore Data Science Glasgow Scotland

3 Rachael Moore Data Analysis Inverness Scotland

Country is dependent on
location, not the ID
 Third Normal Form (3NF)

All Non-Primary Fields are dependent on the Primary Key

ID Forename Surname Subject Location Country

1 Polly Moore Data Engineering Bristol England

2 Chloe Moore Data Science Glasgow Scotland

3 Rachael Moore Data Analysis Inverness Scotland

ID Forename Surname Subject Location Country

1 Polly Moore Data Engineering Bristol England
2 Chloe Moore Data Science Glasgow Scotland
3 Rachael Moore Data Analysis Inverness Scotland
PRACTICE LET’S REVIEW THE DB DESIGN IN OUR SANDBOX
https://coderpad.io/sandbox
 • Constraints are the rules that we can apply on the type of data in a table.

• In other words, we can specify the limit on the type of data that can be stored
in a particular column in a table. Using constraints ensures the accuracy and
reliability of the data in the table.

SQL
• If there is a mismatch or any violation between the constraint we set and the
CONSTRAINT data, then the action that we are trying to perform would be aborted.
TYPES
NOT NULL UNIQUE CHECK

PRIMARY KEY FOREIGN KEY DEFAULT

NB please read about constraints: https://www.studytonight.com/dbms/sql-constraints.php

 • primary key is a single field or combination of fields that uniquely defines a
record

ONLY ONE PRIMARY KEY IN A TABLE

• Must be NOT NULL
• Can be a multiple columns (compound key)
• Can be defined in either a CREATE TABLE statement or an ALTER TABLE
PRIMARY KEY statement

NULL NOT NULL

Default for a column definition Must be specified on column definitions
It means that we are allowed to insert It means we are not allowed to insert NULL
NULL values values. Inserting a NULL would raise an error!
 X

EX
A
NT

AM
SY

PL
E
CREATE TABLE customers CREATE TABLE + TABLE
CREATE TABLE <table_name> NAME
(col1 Type KEY DEFINITION, (customer_id INTEGER PRIMARY KEY, PRIMARY KEY
col2 Type, name VARCHAR(50), COLUMNS
col3 Type);
surname VARCHAR(50) NOT NULL,
telephone INTEGER);
 X

EX
A
NT

AM
SY

PL
E
CREATE TABLE <table_name> CREATE TABLE customers CREATE TABLE + TABLE
(customer_id INTEGER, NAME
(col1 Type,
name VARCHAR(50),
col2 Type,
surname VARCHAR(50) NOT NULL,
col3 Type,
telephone INTEGER,
CONTRAINT CONSTRAINT CONSTRAINT
<constraint_name> pk_ customer _id
<constraint_type> PRIMARY KEY
(<col_that_it_applies_to>) (customer _id)
); );
 Unique PK Table Customers
Unique
customer_id name surname telephone
Column
001 Mary Jones 123-4567
002 Julie Smith 789-4561

Unique column acts as FK in Orders

FOREIGN KEY
Unique PK FK Table Orders

order_No customer_id date item

147A 002 20-08-2019 pizza

258B 001 14-06-2019 salad

NB please read about Foreign Key: http://www.mysqltutorial.org/mysql-foreign-key/

DATA INTEGRITY

DB

source: guru99.com
 DATABASE
RELATIONSHIPS
 ● Primary keys are an example of indexes

● They are automatically set as indexes

● They are best to use with big databases instead of using a non-key or
non-indexed values.

● Instead of scanning the whole table, index allow MySQL to quickly find rows
with a specific value which makes the search quicker

QUICK NOTE: ● More about this in Reference Material

INDEX

NB please read about MySQL Index:https://www.mysqltutorial.org/mysql-index/

 Today we are going to be pizza makers, bakers and small restaurant owners! We
accept orders online or by telephone and deliver pizza to our customers.

We need to create a database to hold information about our customers, so we can

keep records of their names, addresses, phone numbers, email addresses and any
PRACTICE other useful information like placed orders.

TASKS

• Design and create a relational normalised database called customers.

• Set reasonable primary keys to the tables.

• Set NOT NULL constraints on the columns that you think must have
values.

• Let’s do it together!
 PART 2:
SQL CODING
 • DDL stands for "Data Definition Language“.

• It is a subset of SQL statements that create the database schema and change its
structure.

• Defines the columns of the table

• Typically and structural changes of the database schema refer to creating, deleting, or
modifying schema objects such as databases or tables.
CORE COMMANDS
DDL
CREATE DROP

ALTER TRUNCATE

NB please read more about DDL: https://www.w3schools.in/mysql/ddl-dml-dcl/

 • Create a table in your database

CREATE TABLE • Specify table name

• Add column names and data types

 X

EX
A
NT

AM
SY

PL
E
CREATE TABLE <table_name> ( CREATE TABLE customers (
<col_name> <col_data type>, CustomerID int,
<col_name> <col_data type>, FirstName varchar(255)
… LastName varchar(255)
); );
 • Removes table and all data from database

DROP TABLE • BE CAREFUL!

• Error if table is a foreign key to another table

 X

EX
A
NT

AM
SY

PL
E
DROP TABLE <table_name>; DROP TABLE customers;
 • Used to change an existing table

• Add/remove column

• Change column data type

ALTER TABLE
• Change column constraints

• Must comport with current data

 X

EX
A
NT

AM
SY

PL
E
ALTER TABLE <table_name>; ALTER TABLE customers;
RENAME TABLE RENAME TABLE all_customers;
<table_new_name>;
 X

EX
A
NT

AM
SY

PL
E
ALTER TABLE <table_name> ALTER TABLE orders CREATE TABLE + TABLE
NAME
ADD CONSTRAINT ADD CONSTRAINT
<constraint_name> fk_customer_id
<constraint_type> FOREIGN KEY
(<col_that_it_applies_to>)
(customer_id) CONSTRAINT
REFERENCES
REFERENCES
<table_name2>
(<col2_that_it_applies_to>) customers
); (customer_id);
 • DROP deletes the table itself.

• TRUNCATE deletes the data inside of table but not the table itself.

TRUNCATE
TABLE
 X

EX
A
NT

AM
SY

PL
E
TRUNCATE TABLE <table_name>; TRUNCATE TABLE customers;
 • DML stands for "Data Manipulation Language“.

• It is a subset of SQL statements that change the structure of the database schema.

• Typically adds or updates the rows (“tuple”) of the table

CORE COMMANDS
DML
SELECT INSERT

UPDATE DELETE

NB please read more about DML: https://www.w3schools.in/mysql/ddl-dml-dcl/

 • SELECT which data to display and manipulate

SELECT • Use * to show all data

• FROM to specify which table to get data from

 X

EX
A
NT

AM
SY

PL
E
SELECT <col_name> SELECT FirstName SELECT COMMAND

FROM <table_name>; FROM customers; TABLE NAME

SELECT * * to SELECT all data

FROM customers;
 • There are many ways that enable us to constrain the number of results
returned by our query

• Using a DISTINCT Qualifier

SELECT DISTINCT
• It is the keyword, which means that in our query we are asking for a
unique set of results

• In other words we want non-repeating values in the result columns to

be returned
 X

EX
A
NT

AM
SY

PL
What are the fist names

E
of people in my class?
Table name Alias

first_name first_name
SELECT DISTINCT Julie Julie
<alias>.<column_name>, Mary Mary
Mary Joanna
FROM <table_name> Joanna
AS <alias>; Julie

SELECT SELECT DISTINCT

p.first_name, p.first_name,
FROM person FROM person AS
AS p; p;
 • The WHERE clause is a constraint that can be applied to the result set

• The WHERE clause describes the conditions to match for rows to qualify
for result set

WHERE
• It comes after the FROM statement

• It contains Boolean expressions

• Only rows that match a condition are selected for the result set
 X

EX
A
NT

AM
SY

PL
What is the surname of all my

E
classmates who are called Mary?

🡨 SELECT clause
SELECT SELECT
<alias>.<column_name>, p.surname
FROM <table_name> AS FROM person AS p FROM clause

<alias>; WHERE p.name = ‘Mary’ 🡨 WHERE clause

 Use the database PARTS that we created and populated at home

PRACTICE WRITE THE FOLLOWING QUERIES

• Using the table ‘parts’, return all unique part names. What happens if we
want to return all unique parts and their id number? Why?

• Refer to the table ‘projects’ and return all projects that are run in London.
 • INSERT new data in a table

• Two ways to use INSERT:

• Specify column names and values to insert in them
INSERT
• If values are being added to all columns, then no
need to specify the column names BUT make sure
the order of the values is equivalent the order of the
rows.
 X

EX
A
NT

AM
SY

PL
E
INSERT INTO <table_name> INSERT INTO customers
(col1, col2, col3, …) (FirstName,LastName)
VALUES (val1, val2, val3, …)
VALUES (“John”, “Doe”)

INSERT INTO <table_name> INSERT INTO customers Our customer table has
3 columns: CustomerID,
VALUES (val1, val2, val3, …) FirstName and
VALUES (654258, “Jessica”, LastName.
“Day”) 🡨 CustomerID = 654258
🡨 FirstName = “Jessica”
🡨 LastName = “Day”
 • Modifies column(s) in a single table

UPDATE • WHERE clause dictates which rows

• SET keyword follows table name

 X

EX
A
NT

AM
SY

PL
E
UPDATE table_name UPDATE contacts UPDATE COMMAND
TABLE NAME
SET SET SET KEYWORD
table_name.col1 = new_value VALUES
contacts.mobile = 123456789
WHERE WHERE CLAUSE
table_name.col2 = value; WHERE
contacts.surname = ‘Andrews’
 • DELETES one or more rows in a table

• Permanent!
DELETE
• DELETE FROM is actual full command

• WHERE clause is critical!

 X

EX
A
NT

AM
SY

PL
E
DELETE FROM table_name; • DELETE FROM customers; DELETE COMMAND

BAD PRACTICE ☹

DELETE FROM table_name • DELETE FROM customers DELETE COMMAND

WHERE CLAUSE
WHERE • WHERE
table_name.col = value;
• customers.id = 007;

GOOD PRACTICE ☺
 We have our pizzeria customers database. Let’s modify some tables in the
database, so we add Foreign Keys to tables and define relationships
between our tables.
PRACTICE
TASKS

• Add some data to the tables in the customers database

• Alter tables email_address and phone_number in the customers database

by adding Foreign keys that reference Primary keys from relevant tables.

• Remove the table called orders from our database.

 • Revise the slides to re-cap all materials from Session 2.

• Read about Normalisation:

https://www.complexsql.com/database-normalization/

• Read about SQL Commands: https://www.w3schools.in/mysql/ddl-dml-dcl/

HOMEWORK
• Read about Foreign Key: http://www.mysqltutorial.org/mysql-foreign-key/

• Read about Constraints:

https://www.studytonight.com/dbms/sql-constraints.php

USE PARTS DB TO WRITE THE FOLLOWING QUERIES

• Find the name and weight of each red part

• Find all UNIQUE supplier(s) name from London

 • Create a new database called SHOP – we will be using it during next lesson.

• Add a new table called SALES1. It should look like this:

HOMEWORK
THANK YOU
HAVE A GREAT
WEEK!
REFERENCE
MATERIALS
 • A foreign key is a field in a table that matches another field of another table. A
foreign key places constraints on data in the related tables.

FOREIGN KEY • A foreign key can be a column or a set of columns. The columns in the child table
often refer to the primary key columns in the parent table.

• A table may have more than one foreign key, and each foreign key in the child
table may refer to a different parent table.

NB please read about Foreign Key: http://www.mysqltutorial.org/mysql-foreign-key/

 When creating a database, common sense dictates that we use
separate tables for different types of entities.

Some examples are: customers, orders, items and so on. But we

also need to have relationships between these tables. For instance,
customers make orders, and orders contain items.

There are several types of database relationships:

DATABASE One to One Relationships
RELATIONSHIPS One to Many
Many to One Relationships
Many to Many Relationships
 ● Think of it like a book index! Instead of reading through the whole book to
find a certain word, you can look at the index and find the exact page where
the word can be found

● They are best to use with big databases

● Instead of scanning the whole table, index allow MySQL to quickly find rows
with a specific value which makes the search quicker

● More about Indexes: https://www.mysqltutorial.org/mysql-index/

INDEX
 X

EX
A
NT

AM
SY

PL
E
CREATE TABLE customers
CREATE TABLE <table_name> ( (customer_id INT PRIMARY KEY,
col1 INT PRIMARY KEY, Personal_id INT,
col2 INT,
name VARCHAR(50),
col3 INT,
INDEX (c2,c3) ); surname VARCHAR(50) NOT NULL,
telephone INT,
INDEX (personal_id) );
 X

EX
A
NT

AM
SY

PL
E
DROP INDEX <index_name> ON DROP INDEX person_id ON HOW TO DROP INDEX

<table_name>; customers;

DROP INDEX `PRIMARY` ON DROP INDEX `PRIMARY` ON HOW TO DROP A

PRIMARY KEY
<table_name>; customers;

The data remains but it is

no longer an index/PK
 PRIMARY KEY
• Unique identifier of row
• One per table
QUICK • Does not allow NULL
SUMMARY • Single or multiple columns (composite columns)

FOREIGN KEY
• Columns in a table that refer to a Primary Key of another table
• Enforces referential integrity
• Foreign key reinforces relationships between tables:
• One-to-one
• One-to-many
• Many-to-many