1. What is a Database?
A database is a structured collection of data stored electronically, designed to facilitate easy access, management, and updating of that data. You can think of it as a digital filing system where information is organized into tables, making it efficient to retrieve the data you need.
Key Components of a Database:
Data: This refers to raw information, such as names, addresses, or transaction details.
Tables: A database consists of tables that resemble spreadsheets, organized into rows and columns. Each row represents a record (an individual entry), while each column represents a field (a specific piece of information about that entry).
DBMS: A Database Management System (like MySQL, PostgreSQL, or Oracle) provides the tools to create, read, update, and delete data within the database.
2. What is a Relationship?
In general terms, a relationship refers to a connection or association between two or more entities. In the context of databases, relationships define how data in one table relates to data in another. These relationships are essential for organizing and structuring data across multiple tables, helping to avoid redundancy (duplicated data) and enhancing data integrity.
Examples of notations:
3. Types of Database Relationships
A database relationship is a defined connection between two tables, specifying how records in one table relate to records in another. There are three primary types of database relationships:
3.1 One-to-One Relationship
In a one-to-one relationship, each record in Table A corresponds to a single record in Table B, and vice versa. This type of relationship is often used when two tables contain different types of information about the same entity.
Example: Each person has only one passport, and each passport is assigned to only one person.
Schema Diagram:
Notable Points:
Foreign Key Placement: The PersonID is included in the Passport table instead of the Passport ID in the Person table because the passport is dependent on the person. If a person exists, the passport exists; a profile doesn’t make sense without a user. The table that has the dependency contains the foreign key.
Direction of the Relationship: The arrow in database relationship diagrams indicates which table contains the foreign key that references the other. When reading a one-to-one relationship in a database schema, starting from the foreign key (FK) side often provides clearer context.
Here is the sample table explanation
Go lang strcut details
3.2 One-to-Many Relationship
A one-to-many relationship occurs when a single record in one table (the "one" side) can be associated with multiple records in another table (the "many" side). However, each record in the "many" table is linked back to only one record in the "one" table.
Example: One user can create multiple posts. Each post will reference a single user, establishing a one-to-many relationship between the Users and Posts tables.
Characteristics:
Single Entity: The "one" side represents a single entity.
Multiple Associations: The "many" side consists of multiple entities associated with that single entity.
Foreign Key: The "many" table contains a foreign key referencing the primary key of the "one" table.
Table:
Golang struct:
3.3 Many-to-Many Relationship
In a many-to-many relationship, multiple records in one table can be associated with multiple records in another table. This relationship is typically implemented using a junction (or join) table that holds foreign keys referencing the primary keys of both tables.
Example Without a Junction Table
When not using a junction table, you may encounter several drawbacks:
Data Redundancy: You may need to duplicate data across multiple rows, leading to inconsistencies and increased storage requirements.
Limited Flexibility: Not using a junction table restricts your ability to store additional attributes about the relationship itself (e.g., timestamps or status), complicating queries and reducing the richness of your data model.
........
Using Junction Table
Benefits of Using a Junction Table
Reduced Redundancy:
The Users and Roles tables are free from redundancy. Each user and each role is stored only once.
Clear and Manageable Relationships:
The junction table clearly defines the many-to-many relationships without confusion. It simplifies the process of adding or removing roles for users.
Top comments (0)