Skip to content

Commit df0849e

Browse files
committed
fix path
1 parent 148da09 commit df0849e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

01_Relational_Model_Algebra.md renamed to Relation_Algebra/01_Relational_Model_Algebra.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ A major purpose of a database system is to provide users with an abstract view o
7979

8080
## Data Abstraction
8181

82-
![Data Abstraction](imags/dataabstraction.png)
82+
![Data Abstraction](../imags/dataabstraction.png)
8383

8484
For the system to be usable, it must retrieve data efficiently. Designers use complex data structures to represent data in the database to ensure this efficiency. To simplify users’ interactions with the system, data abstraction is categorized into three levels:
8585

@@ -292,7 +292,7 @@ The **Query Processor** simplifies and facilitates data access for users, enabli
292292

293293
Database architecture encompasses the various components of a database system and their interconnections. It is influenced by the underlying computer system and can be categorized into different types:
294294

295-
![Databasearc](imags/dataarch.png)
295+
![Databasearc](../imags/dataarch.png)
296296

297297
## Types of Database Systems
298298
1. **Centralized Systems:** All components run on a single machine.
@@ -310,7 +310,7 @@ Database applications can be organized into two or three tiers:
310310
- **Client Machine:** Hosts the application and communicates directly with the database system using query language statements.
311311
- **Server Machine:** Runs the database system, accessed through Application Program Interface (API) standards like ODBC and JDBC.
312312

313-
![Two-Tier Architecture](imags/two-tier.png)
313+
![Two-Tier Architecture](i../mags/two-tier.png)
314314

315315
### Three-Tier Architecture
316316
- **Client Machine:** Acts as a front end, not making direct database calls.
@@ -319,7 +319,7 @@ Database applications can be organized into two or three tiers:
319319

320320
This architecture is more suitable for larger applications where business logic can be centralized in the application server.
321321

322-
![Three-Tier Architecture](imags/three-tier.png)
322+
![Three-Tier Architecture](../imags/three-tier.png)
323323

324324
---
325325

@@ -383,7 +383,7 @@ The relational model defines a database abstraction based on relations to avoid
383383

384384
## Data Independence
385385

386-
![Data Independence](imags/dataindependence.png)
386+
![Data Independence](../imags/dataindependence.png)
387387

388388

389389
## Relational Model: Keys and Constraints
@@ -428,15 +428,15 @@ The relational model defines a database abstraction based on relations to avoid
428428

429429
Relational Algebra is a set of fundamental operations to retrieve and manipulate tuples in a relation. Each operator takes in one or more relations as inputs, and outputs a new relation. To write queries we can ”chain” these operators together to create more complex operations.
430430

431-
![relationalalgebra](imags/relationalalgebra.png)
431+
![relationalalgebra](../imags/relationalalgebra.png)
432432

433433

434434
---
435435

436436
## Relational Algebra Operations
437437

438438
This document provides an overview of key operations in relational algebra, which is used for querying and manipulating relational databases.
439-
![relational algebra](imags/relational-algebra.png)
439+
![relational algebra](../imags/relational-algebra.png)
440440

441441
### Selection (σ)
442442

0 commit comments

Comments
 (0)