caubert / CSCI_3410 (public) (License: CC BY 4.0) (since 2018-05-16) (hash sha1)
Material for Database Class.
Clone URLs: https://rocketgit.com/user/caubert/CSCI_3410 ssh://rocketgit@ssh.rocketgit.com/user/caubert/CSCI_3410 git://git.rocketgit.com/user/caubert/CSCI_3410
master
List of commits:
Subject Hash Author Date (UTC)
Fixing some of the name of the problems + references. 67c6c669fbb952cdd92be94487f46774da086a59 au 2018-12-21 16:20:08
Exercises fix, naming problems. 2b00c9f2306dd4d05f6919b4c06bc61b5786917f au 2018-12-21 02:10:54
Fixing some exercises. d5053a4b04b16b1817f2e8edb67f9ca7a6c48eb9 au 2018-12-21 01:24:09
Started to externalize the code, fixed the makefile, added a style for HTML files, fixed a lot of solution / problem / exercise environment, cleaned some fig code cfc0c26c5fb9ea64dfd101b9a1a70bc34dfa7082 au 2018-12-20 07:19:10
Re-organization of the structure and of the makefile. d352a7419a507c83374d78c8723d3aaebbaf1e0d au 2018-12-19 02:36:38
Pushing to merge. 92a45b2d1f200221602d730030f87f26e65e335d au 2018-12-19 01:13:42
Pushing to merge. d937aa46e12ee344113794dbb778eccb727819d3 au 2018-12-19 01:09:15
Fixing underline + solution environment. 4f207ab8ae51b1d87d0e83b7b813a91e30bf361f aubert@math.cnrs.fr 2018-12-18 20:03:10
Fixing underline + solution environment. 895823a4d392501285e613325078e9fce7bdd95b aubert@math.cnrs.fr 2018-12-18 20:02:55
Adding info. relative to website aee6744e0c80c31fdf3de459a3265db2211c8b9f aubert@math.cnrs.fr 2018-12-18 14:24:50
Finishing to externalize figures to external files. b7b49588bde465058c526454b938ac27b1447487 aubert@math.cnrs.fr 2018-12-17 20:01:54
Factorizing some aspect, separating fugires, re-wrote makefil, added treatment for html and odt outputs. 91d14fa349fe376408bcc48e4ada948777bda5a0 au 2018-12-17 02:57:14
Fixing project archeticture, tayloring README and moving typesetting section from lecture notes to README. c00c920db70a59ee8626134287aa47455fcb3e03 au 2018-12-16 19:51:52
Fine-tuning makefile 2ce6e9dea5235a97c02b97e548567ff4584c3153 au 2018-12-16 05:41:35
Fixing da441e5483d8153bff9b25f50230f584c4d67c5e au 2018-12-16 05:38:00
re-adding templates. bfe4f6aa774c7befef9eda07f31edb5c9907cedb au 2018-12-16 05:30:19
Restore er tex files. 771634fed59ac3a00fa3fa8ee292e98c4e35e3d6 au 2018-12-16 05:26:43
Changing vect. format from SVG to PDF. fa1276c21b6d139d52bd2c0405a9eb694e1a932d au 2018-12-16 05:25:50
Fixing minor typos 3fd56098f9022b48fadff8e3ea10fd7fcd49213a au 2018-12-16 04:05:47
Re-organization of the project. ccb3e4e35a17076f72b836720948ba7cfe86155b au 2018-12-16 03:16:19
Commit 67c6c669fbb952cdd92be94487f46774da086a59 - Fixing some of the name of the problems + references.
Author: au
Author date (UTC): 2018-12-21 16:20
Committer name: au
Committer date (UTC): 2018-12-21 16:20
Parent(s): 2b00c9f2306dd4d05f6919b4c06bc61b5786917f
Signer:
Signing key:
Signing status: N
Tree: 3bce86e278026f7c151507108edbc701ed1ea94e
File Lines added Lines deleted
notes/lectures_notes.md 19 20
File notes/lectures_notes.md changed (mode: 100644) (index 6153e9e..d82f1f3)
... ... Normalize the relations to 2NF and 3NF. Show all relations at each stage (2NF an
4546 4546
4547 4547 --- ---
4548 4548
4549 Problem +.#book
4549 Problem (Normal Form of the BOOK relation)+.#book
4550 4550 ~ ~
4551 4551
4552 <!-- bug with table -->
4553
4554 4552 Consider the following relation for published books: Consider the following relation for published books:
4555 4553
4556 BOOK (Book\_title, Book\_type, Author\_name, List\_price, Author\_affil, Publisher)
4554 BOOK(Book\_title, Book\_type, Author\_name, List\_price, Author\_affil, Publisher)
4557 4555
4558 4556 Suppose we have the following dependencies: Suppose we have the following dependencies:
4559 4557
4558 <!-- bug with table -->
4560 4559 | | | | | |
4561 4560 ---: | :---: | --- | ---: | :---: | --- |
4562 4561 Book\_title | → | \{ Publisher, Book\_type \} Book\_title | → | \{ Publisher, Book\_type \}
 
... ... Author\_name | → | Author\_affil
4570 4569
4571 4570 --- ---
4572 4571
4573 Problem +.#
4572 Problem (From Business Statements to E.R. Diagram -- UNIVERSITY) +.#BusinessToEr
4574 4573 ~ ~
4575 4574
4576 4575 Consider the following requirements for a UNIVERSITY database, used to keep track of students' transcripts. Consider the following requirements for a UNIVERSITY database, used to keep track of students' transcripts.
 
... ... Problem +.#
4588 4587
4589 4588 --- ---
4590 4589
4591 Problem +.#
4590 Problem (From UML to Relational Model -- DRIVER) +.#UMLtoRELDriver
4592 4591 ~ ~
4593 4592
4594 4593 Consider the UML diagram below, and convert it to the relational model. Consider the UML diagram below, and convert it to the relational model.
 
... ... Problem +.#
4598 4597
4599 4598 --- ---
4600 4599
4601 Problem +.#
4600 Problem (Normal Form of the CONTACT Relation)+.#
4602 4601 ~ ~
4603 4602
4604 4603 Consider the relation Consider the relation
 
... ... Problem +.#
4608 4607 and the following functional dependencies: and the following functional dependencies:
4609 4608
4610 4609 <!-- bug with table --> <!-- bug with table -->
4611
4612 4610 ||| |||
4613 4611 ---: | :---: | --- | ---: | :---: | --- |
4614 4612 \{Zip, Brand\} | → | \{Phone\} \{Zip, Brand\} | → | \{Phone\}
 
... ... Give the relations, their primary keys, and functional dependencies for both ste
4622 4620
4623 4621 --- ---
4624 4622
4625 Problem +.#consultation
4623 Problem (CONSULTATION Relation: Justification, Primary Key and Normal Form)+.#consultation
4626 4624 ~ ~
4627 4625
4628 4626 Consider the relation Consider the relation
 
... ... Problem +.#consultation
4632 4630 with the following functional dependencies: with the following functional dependencies:
4633 4631
4634 4632 <!-- bug with table --> <!-- bug with table -->
4635
4636 4633 ||| |||
4637 4634 ---: | :---: | --- | ---: | :---: | --- |
4638 4635 \{Doctor\_no, Patient\_no, Date\} | → | \{Diagnosis\} \{Doctor\_no, Patient\_no, Date\} | → | \{Diagnosis\}
 
... ... Normalize it to the third normal form if necessary.
4647 4644
4648 4645 --- ---
4649 4646
4650 Problem +.#carinfo
4647 Problem (From E.R. to Relational Schema and UML class diagram -- CAR\_INFO)+.#carinfo
4651 4648 ~ ~
4652 4649
4653 4650 Consider the following E.R. schema for the CAR\_INFO database: Consider the following E.R. schema for the CAR\_INFO database:
 
... ... Problem +.#carinfo
4662 4659
4663 4660 --- ---
4664 4661
4665 Problem +.#mysqlw
4662 Problem (Discovering MySQL Workbench)+.#mysqlw
4666 4663 ~ ~
4667 4664
4668 4665 In this exercise, we will install and explore the basic functionalities of MySQL Workbench, which is a cross-platform, open-source, and free graphical interface for database design. In this exercise, we will install and explore the basic functionalities of MySQL Workbench, which is a cross-platform, open-source, and free graphical interface for database design.
 
... ... Problem +.#mysqlw
4678 4675
4679 4676 --- ---
4680 4677
4681 Problem +.#reverseeng
4678 Problem (Using MySQL Workbench's Reverse Engineering)+.#reverseeng
4682 4679 ~ ~
4683 4680
4684 *This problem requires you to have successfully completed @problem:mysqlw and @problem:ERtoREL.*
4681 *This problem requires you to have successfully completed @problem:mysqlw and @problem:UMLtoRELDriver.*
4685 4682
4686 Using the relational database schema you obtained in @problem:ERtoREL, write the `SQL` implementation of that database.
4687 Then, using MySQL Workbench, use the "Reverse Engineering" function to obtain a E.E.R. diagram of your database, and compare it with the U.M.L. diagram you draw in question~ \ref{ERtoUML} of @problem:ERtoREL.
4688 Apart from the difference inherent to the nature of the diagram (i.e., U.M.L. Vs E.E.R.), how are they the same? How do they differ? Is the automated tool as efficient and accurate as you are?
4683 Using the relational database schema you obtained in @problem:UMLtoRELDriver, write the `SQL` implementation of that database.
4684 Then, using MySQL Workbench, use the "Reverse Engineering" function to obtain a E.E.R. diagram of your database, and compare it with the U.M.L. diagram from @problem:UMLtoRELDriver.
4685 Apart from the difference inherent to the nature of the diagram (i.e., U.M.L. Vs E.E.R.), how are they the same?
4686 How do they differ?
4687 Is the automated tool as efficient and accurate as you are?
4689 4688
4690 4689 --- ---
4691 4690
4692 Problem +.#
4691 Problem (From Business Statements to Dependencies -- KEYBOARD) +.#BusinessToDependecies-KEYBOARD
4693 4692 ~ ~
4694 4693
4695 4694 This exercise asks you to convert business statements into dependencies. This exercise asks you to convert business statements into dependencies.
 
... ... Problem +.#
4709 4708
4710 4709 --- ---
4711 4710
4712 Problem +.#
4711 Problem (Reverse Engineering by Hand)+.#
4713 4712 ~ ~
4714 4713
4715 4714 Look at the following relational model, and "reverse-engineer" it to obtain an E.R. diagram: Look at the following relational model, and "reverse-engineer" it to obtain an E.R. diagram:
 
... ... Problem +.#
4720 4719 ## Solution to Selected Problems ## Solution to Selected Problems
4721 4720
4722 4721 Solution to [%D %n (%T)](#problem:movie) Solution to [%D %n (%T)](#problem:movie)
4723 ~
4722 ~
4724 4723
4725 4724 #. true #. true
4726 4725 #. true #. true
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