eth-janishutz/eth-summaries
1
0
Fork 0
mirror of https://github.com/janishutz/eth-summaries.git synced 2026-07-27 21:29:09 +02:00
Code Issues Packages Projects Releases Wiki Activity

[DMDB] Intro

Browse Source
This commit is contained in:
janishutz
2026-06-22 09:58:03 +02:00
parent 9806123eb7
commit cef70242ce
6 changed files with 36 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
semester4/dmdb/data-modelling-databases-summary.pdf
BIN
View File
Binary file not shown.
semester4/dmdb/data-modelling-databases-summary.tex
+22 -5
View File
@@ -4,6 +4,7 @@
\setupGlossary \setupGlossary
\input{glossary/main.tex} \input{glossary/main.tex}
\setGlossaryMarkup
\usepackage{lmodern} \usepackage{lmodern}
\setFontType{sans} \setFontType{sans}
@@ -33,8 +34,10 @@
FS2026, ETHZ FS2026, ETHZ
\begin{Large} \begin{Large}
Summary of the Script and Lectures Summary of the Lecture Slides
\end{Large} \end{Large}
\url{https://systems.ethz.ch/education/courses/2026-spring/dmdb.html}
\end{center} \end{center}
\newpage \newpage
@@ -50,11 +53,25 @@ This summary assumes some basic knowledge about databases.
All words written in \textbf{bold} should be clickable and should link you to the corresponding term in the glossary. All words written in \textbf{bold} should be clickable and should link you to the corresponding term in the glossary.
If I did not forget a term that is, of course. If I did not forget a term that is, of course.
\subsection{IMS}
Early databases were not relational and they also required the user of the system to know \textit{how the data was stored}.
This of course is not ideal, as any update to the data structure also required an update to the code interacting with it.
In addition, manual query optimization has to be done.
\newsection Non-relational databases commonly have data redundancy, due to non-hierarchical applications being forced into a tree-based model.
\section{SQL} This causes issues when updating the data, as one needs to update the data in all places where a copy of the data exists.
\input{parts/00_sql/00_intro.tex}
\input{parts/00_sql/01_operations.tex} \subsection{Network Model}
In a network model, one \gls{record} is fetched at a time, so it essentially traverses the network.
However, we again do not have data independence, thus the application again needs to change when the physical data representation changes.
In addition, manual query optimization has to happen again, thus, any change to the physical data representation may cause the need to redo the optimization.
\subsection{Relational Model}
\bi{This is the focus of this course}
\include{parts/00_sql/main.tex}
\include{parts/01_relational-logic/main.tex}
\printGlossary \printGlossary
semester4/dmdb/glossary/basics.tex
+4 -4
View File
@@ -6,7 +6,7 @@
name={imperative}, name={imperative},
description={Describes how to achieve something} description={Describes how to achieve something}
} }
% \newglossaryentry{}{ \newglossaryentry{record}{
% name={}, name={record},
% description={} description={}
% } }
semester4/dmdb/parts/00_sql/00_intro.tex
+1 -1
View File
@@ -1 +1 @@
\refacr{sql} is a \refgls{declarative} programming language, used to describe and operate on databases. \acrshort{sql} is a \gls{declarative} programming language, used to describe and operate on databases.
semester4/dmdb/parts/00_sql/main.tex
+5
View File
@@ -0,0 +1,5 @@
\newsection
\section{SQL}
\input{parts/00_sql/00_intro.tex}
\input{parts/00_sql/01_operations.tex}
% \input{parts/00_sql/}
semester4/dmdb/parts/01_relational-logic/main.tex
+4
View File
@@ -0,0 +1,4 @@
\newsection
\section{Relational Logic \& Algebra}
\input{parts/01_relational-logic/00_intro.tex}
% \input{parts/01_relational-logic/}