PART 1 - READING ASSIGNMENT (Modern Database Management)

Ch.4. Logical Database Design and the Relational Model

PART 2 - READING ASSIGNMENT (Beginning MySQL)
Ch.4. Designing a Relational Database

PART 3 - READING ASSIGNMENT (Beginning Database Design Solutions)
Ch.7. Normalizing Data
Ch.8. Designing Databases to Support Software Applications

PART 4 - Do Problems & Exercises 1a, 2a, 4a, 5 from Modern DBMS (Page 195)

PART 5 - Do all the exercises at the end of Chapter 4 (Beginning MySQL)

PART 6 - Do all the exercises at the end of Chapter 7, 8 (Beginning Database Design)
The
goal of all normalized data is to prevent lost data and inconsistent data, while minimizing redundant data.
Each column in a row must be atomic. In other words, the column can contain only one value
for any given row.
q Each row in a table must contain the same number of columns. Given that each column can contain
only one value, this means that each row must contain the same number of values.
q All rows in a table must be different. Although rows might include the same values, each row,
when taken as a whole, must be unique in the table

A primary key made up of more than one column is referred to as a composite primary key.
manage persons lo oka button manage customers ani petu
inkokati manage supplier employee ani petu
danlo
suppliers ni combo box peti select chesina suppliers employees ni manage cheyi



Normalization:
Another way to make a database more flexible and robust is to normalize it. Normalization
makes the database more able to accommodate changes in the structure of the data. It also protects
the database certain kinds of errors.

Depending on how you design a relational database, it may be susceptible so all sorts of problems

It may contain lots of duplicated data. This not only wastes space but it also makes updating
all of those duplicated values a time-consuming chore.

It may incorrectly associate two unrelated pieces of data so you cannot delete one without
deleting the other.

It may require a piece of data that shouldnt exist in order to represent another piece of data
that should exist

It may limit the number of values that you can enter for what should be a multi-valued
piece of data.

In database terminology, these issues are called anomalies. (Anomaly is a euphemism for problem.
Normalization is a process of rearranging the database to put it into a standard (normal) form that
prevents these kinds of anomalies.
There are seven different levels of normalization. Each level includes those before it.
That means if a database is at one level of normalization, then by definition it gets the
advantages of the lower levels.
The different levels of normalization in order from weakest to strongest are:
First Normal Form (1NF)
Second Normal Form (2NF)
Third Normal Form (3NF)
Boyce-Codd Normal Form (BCNF)
Fourth Normal Form (4NF)
Fifth Normal Form (5NF)
Domain/Key Normal Form (DKNF)
The official qualifications for 1NF are:
Each column must have a unique name.

The order of the rows and columns doesnt matter.
Each column must have a single data type.
No two rows can contain identical values.
Each column must contain a single value.
Columns cannot contain repeating groups