List of commits:
Subject Hash Author Date (UTC)
fixed couple of typos. 6191d6cc01638c07ab0b48a086718fc2440fa367 caubert 2021-03-12 18:31:47
Added quiz #2$ ff134e831427d6e24603af76be52576928dae301 caubert 2021-03-01 19:51:12
Added missing file. d7f2b8ceb14456db8ee2857fcd2b9445bcff1f95 caubert 2021-02-16 18:54:57
Added more complex queries and triggers for HW_Vaccine. 1b133f143e9c6fec72271de28345df39689235f8 caubert 2021-02-09 20:23:30
Added project 1 and its solution. 14f03a1733c084b26dbc72c009e2b7b832ed8643 caubert 2021-02-06 21:46:04
Added project 1 and its solution. b7a31871ebccbf4caff81d9d57ed6847f4dc5543 caubert 2021-02-06 21:45:24
Added simple examples for SQL. 4ea62f6930ff19bcff8d406d95c9cd84c0f0216d caubert 2021-02-02 22:24:41
Added first project. e851058cc58a9d47ada9970f8b914e798c7d2ce7 caubert 2021-01-27 19:57:12
Few typos. 45ba15cd03fab4388439b617c656f52b2ec96319 caubert 2021-01-26 20:08:24
Small fix in code. 7860e391d0bbe82336b8f05585f846e829d181b1 caubert 2021-01-26 18:55:17
Fixed various bugs. fa76c1e469a4263d7bb7da79532abd1eedcc49be caubert 2021-01-22 19:27:01
First quizz, and fix bug with code displayed. bc9b6bb097e30186805b02dc1cdc5de2d5feabe4 caubert 2021-01-22 19:21:54
Edited the preamble. 364e709107602e163ea9365f25ccf1f5a6bb1914 caubert 2021-01-11 16:00:07
Started to edit notes and add final exam from fall 2020. bb747e27ce08ce17e91913e947614e3057580995 caubert 2021-01-06 22:26:07
Integrated the include-link feature of pandoc-include-code. 3a8f9ededdaa1f05d526742f5d447aaa017e1d1b caubert 2021-01-04 22:52:18
Fixed citeproc. 0d90c7e60e4a4474fd7ded03bb6526ea63a57253 aubert@math.cnrs.fr 2020-12-27 21:33:48
(Finally) updated pandoc and pandoc-numbering. 127c1964a0732b49e14b46fdb0d3f8446e3892d0 aubert@math.cnrs.fr 2020-12-27 21:14:31
Fixed url in comments, avoid them being wrapped. 09a6a78479f24b5749605a4cb7136f8cfbf57d30 aubert@math.cnrs.fr 2020-12-18 18:55:50
Added comments on procedures from code f3e9c2abac41d5de1c7473867c4f688051dec928 aubert@math.cnrs.fr 2020-12-01 15:46:53
Updated mysql connector 228d86db5498aae94a4d162272fa03a84ae9c532 aubert@math.cnrs.fr 2020-12-01 15:09:46
Commit 6191d6cc01638c07ab0b48a086718fc2440fa367 - fixed couple of typos.
Author: caubert
Author date (UTC): 2021-03-12 18:31
Committer name: caubert
Committer date (UTC): 2021-03-12 18:31
Parent(s): ff134e831427d6e24603af76be52576928dae301
Signer:
Signing key:
Signing status: N
Tree: f4908c493fba22e30d9520230930beddf81351c6
File Lines added Lines deleted
notes/lectures_notes.md 11 7
File notes/lectures_notes.md changed (mode: 100644) (index a141919..212c047)
... ... You can have a look at e.g. <http://holowczak.com/converting-e-r-models-to-relat
6126 6126
6127 6127 What makes a good database? What makes a good database?
6128 6128 At the logical (conceptual) and physical (implementation) levels. At the logical (conceptual) and physical (implementation) levels.
6129 We will answer belowe this question broadly, and will then use the concept of _functional dependency_ to capture some of those notions precisely, mathematically, and be able to detect issues preventing our database from meeting the usual goals.
6129 6130
6130 Goals:
6131 In general, a good data base should:
6131 6132
6132 #. Information preservation (and avoid loss of information)
6133 #. Minimum redundancy
6134 #. Make queries easy (avoid redundant work, make `SELECT` and select-project-join easy)
6133 #. Enforces information preservation (and avoid loss of information)
6134 #. Have minimum redundancy
6135 #. Makes queries easy (avoid redundant work, make `SELECT` and select-project-join easy)
6136
6137 Normally, consistency will simply follows if those goals are met.
6135 6138
6136 6139 For ER diagrams, some of the usual techniques^[Cf. for instance <http://infolab.stanford.edu/~ullman/fcdb/aut07/slides/er.pdf>.] are: For ER diagrams, some of the usual techniques^[Cf. for instance <http://infolab.stanford.edu/~ullman/fcdb/aut07/slides/er.pdf>.] are:
6137 6140
 
... ... Solution to [%D %n (%T)](#problem:movie)
8047 8050 Solution to [%D %n (%T)](#problem:car-insurance) Solution to [%D %n (%T)](#problem:car-insurance)
8048 8051 ~ ~
8049 8052 A possible solutions is A possible solutions is
8053
8054 ![](fig/er/accident)
8055 \
8056
8050 8057 <!-- <!--
8051 8058 Re-work on that solution? Re-work on that solution?
8052 8059
8053 8060 ![ER Diagram Car Insurance](img/car_example) ![ER Diagram Car Insurance](img/car_example)
8054
8055 8061 --> -->
8056 8062
8057 ![](fig/er/accident)
8058 \
8059 8063
8060 8064 --- ---
8061 8065
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/caubert/CSCI_3410

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/caubert/CSCI_3410

Clone this repository using git:
git clone git://git.rocketgit.com/user/caubert/CSCI_3410

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main