remove non sql files

This commit is contained in:
SowinskiBraeden committed 2025-11-28 16:32:11 -08:00
1 parent 9b8a13f429
commit d676f7d68c
7 files changed
+2 -23

No files matched your search

+2
View File
@@ -0,0 +1,2 @@
*.pdf
*.txt
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
-14
View File
@@ -1,14 +0,0 @@
Almost all the tables and or constraints caused errors, so I had to spend a lot of time, updating the lab5 schema sql file to accomodate the data given for lab 6 as well as update some constraints to ensure all the insertions worked as intended.
Here is an example of some of the error messages given while attemping to delete data in task 4 that is referenced by entities in other tables.
psql:lab6_dml.sql:322: ERROR: update or delete on table "department" violates foreign key constraint "professor_dep_code_fkey" on table "professor"
DETAIL: Key (dep_code)=(COMP) is still referenced from table "professor".
psql:lab6_dml.sql:325: ERROR: column "off_sectoin" does not exist
LINE 2: WHERE off_sectoin = 'L2';
^
HINT: Perhaps you meant to reference the column "course_offering.off_section".
psql:lab6_dml.sql:328: ERROR: update or delete on table "location" violates foreign key constraint "department_loc_code_fkey" on table "department"
DETAIL: Key (loc_code)=(SE12 260) is still referenced from table "department".
Finally, I think the schema is much better not only to fit the data given but being correct and making sense logically on what data should be there, and what their constraints should be to better reflect the real world.
-9
View File
@@ -1,9 +0,0 @@
Yes, all of the row counts make sense, there may be some duplicatoin.
For example, when we are getting all student ids, and their enrollments, there may be duplicate enrollment data.
i.e. two students are enrolled in the same course_offering. However, we since we are showing the student_id we are able to tell them apart.
I dont think distinct would change the result in the example above, there is student x enrolled in class A, and student y enrolled in class A too. Those are already distinct.
I think for the most part I am selecting the minimul necessary columns, only showing relavent related information.
Unless asked to show all data of a table.