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)
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
Updated java beautifier 30f4a79f2d911cd0b6a24c31f968f0d23620965f aubert@math.cnrs.fr 2020-12-01 15:07:50
Worked on procedure example from java 998ea14119a5a3f88efc4b0a126177e85151e43d aubert@math.cnrs.fr 2020-12-01 15:06:47
Brief example of calling a procedure from a program. 1054c9d5c83fb956bdd0b8d884d5ce2c8a9a640e aubert@math.cnrs.fr 2020-11-30 19:00:45
Added solution to second exam d8f62ded96991885a96d561db587988d453a28c8 aubert@math.cnrs.fr 2020-11-05 20:35:50
Quick fix on testing semicolons. 7f48d88d2ed69213d803a7736df3d50330cfecd1 aubert@math.cnrs.fr 2020-11-03 14:14:06
Added simple example to test if semicolon are important in SQL querries. 98097fb11558c08bad630fb3351f99ceb6777de7 aubert@math.cnrs.fr 2020-11-03 14:11:22
Updated spots to https. a8daf1768395aa296bf0dd05783dd53c757d5d19 aubert@math.cnrs.fr 2020-10-05 16:18:44
Adding quiz #2 98e0ae5b8ce766524f60c91adb1040235e1bbf31 aubert@math.cnrs.fr 2020-10-02 19:00:15
Commit 45ba15cd03fab4388439b617c656f52b2ec96319 - Few typos.
Author: caubert
Author date (UTC): 2021-01-26 20:08
Committer name: caubert
Committer date (UTC): 2021-01-26 20:08
Parent(s): 7860e391d0bbe82336b8f05585f846e829d181b1
Signer:
Signing key:
Signing status: N
Tree: 1393f339dc2e6965e227439658e7acf094c21a86
File Lines added Lines deleted
notes/code/sql/HW_CapstoneSol.sql 26 36
notes/lectures_notes.md 1 0
File notes/code/sql/HW_CapstoneSol.sql changed (mode: 100644) (index 1c14b77..423d6b7)
... ... You can simply answer "True" or "False", or justify your reasoning (e.g. with co
124 124 */ */
125 125 -- 1. Can a project uses multiple programming languages? -- 1. Can a project uses multiple programming languages?
126 126 -- Yes. -- Yes.
127 -- 2. Can a student be the leader of multiple
127 -- 2. Can a student be the leader of multiple
128 -- projects?
128 129 -- Yes. -- Yes.
129 -- 3. Can multiple projects have the same code name?
130 -- 3. Can multiple projects have the same code name?
130 131 -- Yes. -- Yes.
131 -- 4. Could Claude simply enter NULL for the value
132 -- project's code name, since he's undecided?
133 -- No.
134 -- 5. Can a project be created without project
135 -- No.
136 -- 6. Can we know who is working on a project
137 -- its leader?
138 -- No.
132 -- 4. Could Claude simply enter NULL for the value
133 -- of his pproject's code name, since he's undecided?
134 -- No.
135 -- 5. Can a project be created without project
136 -- leader?
137 -- No.
138 --6. Can we know who is working on a project
139 -- without being its leader?
140 -- No.
139 141 /* /*
140 142
141 143 II. Relational Model (6 pts.) II. Relational Model (6 pts.)
 
... ... VALUES (
173 169 NULL); NULL);
174 170
175 171 -- 2. Write a command that updates the code name of the -- 2. Write a command that updates the code name of the
176 -- project ("Undecided", "9999999999999") to "VR in
172 -- project ("Undecided", "9999999999999") to "VR in
173 -- ER".
177 174 UPDATE UPDATE
178 175 PROJECT PROJECT
179 176 SET CodeName = "VR in ER" SET CodeName = "VR in ER"
 
... ... WHERE CodeName = "Undecided"
182 178 AND Leader = "9999999999999"; AND Leader = "9999999999999";
183 179
184 180 -- 3. Write a command that updates the graduation year of the -- 3. Write a command that updates the graduation year of the
185 -- student whose id is "0987654321098" to 2024, and
186 -- semester to "Fall".
181 -- student whose id is "0987654321098" to 2024, and
182 -- the semester to "Fall".
187 183 UPDATE UPDATE
188 184 STUDENT STUDENT
189 185 SET GraduationYear = 2024, SET GraduationYear = 2024,
 
... ... SET GraduationYear = 2024,
192 187 WHERE id = "0987654321098"; WHERE id = "0987654321098";
193 188
194 189 -- 4. Write a command that changes the STUDENT table to make -- 4. Write a command that changes the STUDENT table to make
195 -- it impossible to enter NULL for the first name of
196 -- student, without changing the primary key.
190 -- it impossible to enter NULL for the first name of
191 -- a student, without changing the primary key.
197 192 ALTER TABLE STUDENT MODIFY FName VARCHAR(50) NOT NULL; ALTER TABLE STUDENT MODIFY FName VARCHAR(50) NOT NULL;
198 193
199 194 -- 5. Write a command that changes the datatype of -- 5. Write a command that changes the datatype of
200 -- GraduationYear to SMALLINT.
195 -- GraduationYear to SMALLINT.
201 196 ALTER TABLE STUDENT MODIFY GraduationYear SMALLINT; ALTER TABLE STUDENT MODIFY GraduationYear SMALLINT;
202 197
203 198 -- 6. Write a command that adds an attribute "ReleaseDate" to -- 6. Write a command that adds an attribute "ReleaseDate" to
204 -- the PROJECT table.
199 -- the PROJECT table.
205 200 ALTER TABLE PROJECT ALTER TABLE PROJECT
206 201 ADD COLUMN ReleaseDate DATE; ADD COLUMN ReleaseDate DATE;
207 202
208 203 -- 6.bis If you managed to write the previous command -- 6.bis If you managed to write the previous command
209 -- correctly, write a command that sets the release
210 -- the project ("Brick Break", "0123456789100") to
211 -- of November 2022.
204 -- correctly, write a command that sets the release
205 -- date of the project ("Brick Break", "0123456789100") to
206 -- the 26th of November 2022.
212 207 UPDATE UPDATE
213 208 PROJECT PROJECT
214 209 SET ReleaseDate = DATE "20221126" SET ReleaseDate = DATE "20221126"
 
... ... WHERE CodeName = "Brick Break"
221 211 AND Leader = "0123456789100"; AND Leader = "0123456789100";
222 212
223 213 -- 7. Write a command that makes it impossible for a student -- 7. Write a command that makes it impossible for a student
224 -- to be the leader in more than one project
225 -- (This command should return an error)
226 -- ALTER TABLE PROJECT ADD UNIQUE (Leader);
214 -- to be the leader in more than one project
215 -- (This command should return an error)
216 -- ALTER TABLE PROJECT ADD UNIQUE (Leader);
File notes/lectures_notes.md changed (mode: 100644) (index bcac630..aa72ea4)
... ... Note that we were quite careless when we set-up our installation:
2908 2908 - We did not impose any requirement on the root password of our installation. Using a good, secure, and unique password, should have been required / advised. - We did not impose any requirement on the root password of our installation. Using a good, secure, and unique password, should have been required / advised.
2909 2909 - We left all the options on default, whereas a good, secure, installation, always fine-tune what is enabled and what is not. - We left all the options on default, whereas a good, secure, installation, always fine-tune what is enabled and what is not.
2910 2910 - We chosed a very weak password for `testuser` that is common to all of our installation. - We chosed a very weak password for `testuser` that is common to all of our installation.
2911 - Using the command `mysqldump -u testuser -ppassword` means that the password will be stored in the history of your command-line interface (that you should be able to access using `history` or `Get-History` for Powershell) and could be accessed by anyone having access to it.
2911 2912
2912 2913 All of those are obvious security risks, and **make this installation unsafe to be a production environment**. All of those are obvious security risks, and **make this installation unsafe to be a production environment**.
2913 2914 We will only use it as a testing / learning environment, but it is strongly recommended to: We will only use it as a testing / learning environment, but it is strongly recommended to:
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