Welcome to the World of Databases!
Ever wondered how Netflix remembers exactly which episode of your favorite show you watched last? Or how a school keeps track of thousands of students, their grades, and their attendance without getting hopelessly lost? The answer is databases. In this chapter, we are going to explore how data is organized, linked, and moved around. Don't worry if this seems a bit technical at first—we’ll break it down using everyday examples!
1. Flat Files vs. Relational Databases
Before we look at the fancy stuff, we need to understand the two main ways data is stored.
The Flat File Database
Imagine a single, giant spreadsheet where every single piece of information is crammed into one table. This is a Flat File database. While it’s simple to set up, it has big problems:
1. Data Redundancy: You end up typing the same information over and over (like a customer's address every time they buy something).
2. Data Integrity: If a customer moves house, you have to find every single row they are in and change the address. If you miss one, your data is now wrong!
The Relational Database
A Relational Database is much smarter. Instead of one big table, we split the data into several smaller tables (like a 'Customers' table and an 'Orders' table) and link them together.
Example: Instead of writing a customer's name 50 times for 50 orders, you write it once in the Customers table and just use a "Customer ID" to link it to their orders.
Quick Review: Flat files are okay for a simple shopping list, but for anything complex, we use Relational Databases to save space and prevent errors.
2. The "Keys" to Success
In a relational database, we use Keys to keep everything organized and connected.
Primary Key: This is a unique identifier for every record in a table. It must be unique—no two records can have the same one.
Example: Your Student ID number or a Passport number.
Foreign Key: This is a field in one table that is a Primary Key in another table. It acts as the "bridge" or link between the two.
Example: In an 'Orders' table, the 'CustomerID' is a Foreign Key that points back to the 'Customers' table.
Secondary Key: This is a field that is used for searching or indexing data quickly. It doesn't have to be unique.
Example: If you call a shop, they might ask for your "Surname" to find your account. "Surname" is the Secondary Key because it’s easier to remember than a random ID number.
Memory Trick:
Primary = Personal (Your unique ID).
Foreign = Friend (A link to another table).
Secondary = Search (Used to find things fast).
3. Entity Relationship (ER) Modelling
An Entity is just a "thing" we want to store data about (like a Student, a Book, or a Car). ER Modelling is drawing a diagram to show how these things are related to each other.
There are three main types of relationships:
1. One-to-One (1:1): One person has one passport.
2. One-to-Many (1:M): One mother can have many children, but each child has only one biological mother.
3. Many-to-Many (M:M): Many students study many subjects. (Note: Relational databases don't like M:M relationships directly; they usually need a 'link table' in the middle to break it down!)
Did you know? When drawing these, we often use "Crow's Foot" notation. A single line means "one" and a symbol that looks like a bird's foot means "many."
4. Capturing, Selecting, and Managing Data
Now that we have a structure, how do we actually use the data? There are four main steps in the life of data:
Capturing Data
This is getting the data into the database.
- Manual: Typing it into an online form.
- Automatic: Using OCR (Optical Character Recognition) to read printed text, or scanning a barcode at a supermarket.
Selecting Data
This is choosing specifically what you want to see. You don't usually want to see the whole database; you just want "all students in Year 12." We use Queries (usually written in a language called SQL) to "filter" the data and show only what we need.
Managing Data
This involves keeping the database healthy. It includes Updating (changing a phone number), Deleting (removing an old account), and Sorting the data into a useful order.
Exchanging Data
Sometimes, we need to send data from our database to a different computer system. To do this, we use standard formats that everyone understands:
- CSV (Comma Separated Values): A simple text file where data is separated by commas.
- XML or JSON: More modern formats that are used to send data over the internet between apps.
Common Mistake: Students often think "Capturing" and "Exchanging" are the same. Remember: Capturing is getting data in; Exchanging is moving data between systems.
5. Summary Key Takeaways
1. Relational Databases use multiple linked tables to reduce repeated data (redundancy).
2. Primary Keys are unique IDs; Foreign Keys are the links between tables.
3. ER Diagrams help us visualize how entities (like 'Customer' and 'Product') relate to each other.
4. Data Exchange relies on common formats like CSV or JSON so different systems can "talk" to each other.
Keep practicing! Databases are all about logic. Once you see the "links" between the tables, the whole system starts to make sense. You've got this!