Skip to content

Commit 2b1e38f

Browse files
Merge pull request #2 from dimitri-yatsenko/claude/fix-myst-warnings-01FnWNTWHSr7VrVJBTDBMdLu
Fix MyST build warnings and configuration issues
2 parents 06e377e + dac03b4 commit 2b1e38f

12 files changed

Lines changed: 226 additions & 324 deletions

File tree

book/00-introduction/25-history.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ DataJoint's evolution from lab tool to commercial platform reflects its growing
66

77
```{image} ../images/cave-art.jpg
88
---
9-
:alt: cave painting
10-
:width: 600px
9+
alt: cave painting
10+
width: 600px
1111
---
1212
```
1313
## Academic Origins: From Lab Tool to Open-Source Project

book/20-concepts/02-relational.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,6 @@ The most common way to interact with relational databases is through the Structu
203203
When speaking with database programmers and computer scientists, you will often run into different terminologies. Practical database programmers speak of tables and rows while theoretical data modelers may describe the same things as *relations* and *tuples*.
204204

205205
:::{table} The difference in terminology used in relational theory and relational databases.
206-
:widths: auto
207206
:align: center
208207
| Relational Theory | Database Programming & SQL | Description |
209208
|:--|:--|:--|

book/20-concepts/04-workflows.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,6 @@ Several different notations have been developed, including Chen's original notat
8484
:::{figure}
8585
:align: center
8686
```{mermaid}
87-
---
88-
title: Crow's Foot notation.
89-
---
9087
erDiagram
9188
EMPLOYEE }o--o{ PROJECT : assigned-to
9289
```
@@ -97,9 +94,6 @@ Or using an explicit association table:
9794
:::{figure}
9895
:align: center
9996
```{mermaid}
100-
---
101-
title: Crow's Foot notation.
102-
---
10397
erDiagram
10498
EMPLOYEE ||--o{ ASSIGNMENT : works-on
10599
ASSIGNMENT }o--|| PROJECT : assigned-to

book/20-concepts/concepts-quiz.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1076,7 +1076,6 @@ E) It eliminates all human judgment
10761076

10771077
```{list-table} Grade Scale
10781078
:header-rows: 1
1079-
:widths: 20 20 60
10801079
10811080
* - Score Range
10821081
- Percentage

book/30-database-design/010-schema.ipynb

Lines changed: 2 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -3,49 +3,7 @@
33
{
44
"cell_type": "markdown",
55
"metadata": {},
6-
"source": [
7-
"---\n",
8-
"title: Create Schemas\n",
9-
"authors:\n",
10-
" - name: Dimitri Yatsenko\n",
11-
" - date: 2025-01-12\n",
12-
"---\n",
13-
"\n",
14-
"# What is a schema?\n",
15-
"\n",
16-
"The term schema has two related meanings in the context of databases:\n",
17-
"\n",
18-
"## 1. Schema as a Data Blueprint\n",
19-
"A **schema** is a formal specification of the structure of data and the rules governing its integrity.\n",
20-
"It serves as a blueprint that defines how data is organized, stored, and accessed within a database.\n",
21-
"This ensures that the database reflects the rules and requirements of the underlying business or research project it supports.\n",
22-
"\n",
23-
"In structured data models, such as the relational model, a schema provides a robust framework for defining:\n",
24-
"* The structure of tables (relations) and their attributes (columns).\n",
25-
"* Rules and constraints that ensure data consistency, accuracy, and reliability.\n",
26-
"* Relationships between tables, such as primary keys (unique identifiers for records) and foreign keys (references to related records in other tables).\n",
27-
"\n",
28-
"### Aims of Good Schema Design\n",
29-
"* **Data Integrity**: Ensures consistency and prevents anomalies.\n",
30-
"* **Query Efficiency**: Facilitates fast and accurate data retrieval, supports complex queries, and optimizes database performance.\n",
31-
"* **Scalability**: Allows the database to grow and adapt as data volumes increase.\n",
32-
"\n",
33-
"### Key Elements of Schema Design\n",
34-
"* **Tables and Attributes**: Each table is defined with specific attributes (columns), each assigned a data type.\n",
35-
"* **Primary Keys**: Uniquely identify each record in a table.\n",
36-
"* **Foreign Keys**: Establish relationships between entities in tables.\n",
37-
"* **Indexes**: Support efficient queries.\n",
38-
"\n",
39-
"Through careful schema design, database architects create systems that are both efficient and flexible, meeting the current and future needs of an organization. The schema acts as a living document that guides the structure, operations, and integrity of the database.\n",
40-
"\n",
41-
"## 2. Schema as a Database Module\n",
42-
"\n",
43-
"In complex database designs, the term \"schema\" is also used to describe a distinct module of a larger database with its own namespace that groups related tables together. \n",
44-
"This modular approach:\n",
45-
"* Separates tables into logical groups for better organization.\n",
46-
"* Avoids naming conflicts in large databases with multiple schemas.\n",
47-
"\n"
48-
]
6+
"source": "---\ntitle: Create Schemas\nauthors:\n - name: Dimitri Yatsenko\n---\n\n# What is a schema?\n\nThe term schema has two related meanings in the context of databases:\n\n## 1. Schema as a Data Blueprint\nA **schema** is a formal specification of the structure of data and the rules governing its integrity.\nIt serves as a blueprint that defines how data is organized, stored, and accessed within a database.\nThis ensures that the database reflects the rules and requirements of the underlying business or research project it supports.\n\nIn structured data models, such as the relational model, a schema provides a robust framework for defining:\n* The structure of tables (relations) and their attributes (columns).\n* Rules and constraints that ensure data consistency, accuracy, and reliability.\n* Relationships between tables, such as primary keys (unique identifiers for records) and foreign keys (references to related records in other tables).\n\n### Aims of Good Schema Design\n* **Data Integrity**: Ensures consistency and prevents anomalies.\n* **Query Efficiency**: Facilitates fast and accurate data retrieval, supports complex queries, and optimizes database performance.\n* **Scalability**: Allows the database to grow and adapt as data volumes increase.\n\n### Key Elements of Schema Design\n* **Tables and Attributes**: Each table is defined with specific attributes (columns), each assigned a data type.\n* **Primary Keys**: Uniquely identify each record in a table.\n* **Foreign Keys**: Establish relationships between entities in tables.\n* **Indexes**: Support efficient queries.\n\nThrough careful schema design, database architects create systems that are both efficient and flexible, meeting the current and future needs of an organization. The schema acts as a living document that guides the structure, operations, and integrity of the database.\n\n## 2. Schema as a Database Module\n\nIn complex database designs, the term \"schema\" is also used to describe a distinct module of a larger database with its own namespace that groups related tables together. \nThis modular approach:\n* Separates tables into logical groups for better organization.\n* Avoids naming conflicts in large databases with multiple schemas."
497
},
508
{
519
"cell_type": "markdown",
@@ -264,4 +222,4 @@
264222
},
265223
"nbformat": 4,
266224
"nbformat_minor": 2
267-
}
225+
}

0 commit comments

Comments
 (0)