-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
632 changed files
with
239,872 additions
and
2,580 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| --- | ||
| title: "CS133-lecture-20210519" | ||
| # date: 2021-05-19T09:43:57-07:00 | ||
| draft: false | ||
| bookToc: true | ||
| tags: ["app distribution"] | ||
| --- | ||
|
|
||
| ## Mobile development – App distribution | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ### Certificates, UDID, signing authorities | ||
|
|
||
|  | ||
|  | ||
|  | ||
|
|
||
| ### Signing and distribution | ||
|
|
||
|  | ||
|  | ||
|  | ||
|  | ||
|  | ||
|  | ||
|  | ||
|
|
||
| ### Building native apps using CN1 | ||
|
|
||
|  | ||
|  | ||
|  | ||
|  | ||
|
|
||
| ### Downloading/installing native apps | ||
|
|
||
|  | ||
|  | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| --- | ||
| title: "CS134-lecture-20210601" | ||
| # date: 2021-06-01T11:34:27-07:00 | ||
| draft: false | ||
| bookToc: true | ||
| tags: ["syllabus", "DBMS"] | ||
| --- | ||
|
|
||
| # Course orientation | ||
|
|
||
| ## Syllabus | ||
|
|
||
| {{< hint info >}} | ||
| [134Sy_Summer2021.pdf](/notes/134Sy_Summer2021.pdf) | ||
| {{< /hint >}} | ||
|
|
||
| ## Notes during orientation | ||
|
|
||
| - 5 assignments, 5 weekly homeworks | ||
| - Effort may be taken into account during assignment grading | ||
| - Assignments build upon the previous assignment | ||
| - Midterm on June 22, and final on last day | ||
|
|
||
| ## Introduction to database management systems | ||
|
|
||
|  | ||
|  | ||
|
|
||
| {{< columns >}} | ||
| Files | ||
| - persistent | ||
| - on disk | ||
| - easy to work with | ||
| <---> | ||
| DBMS | ||
| - needs knowledge of software | ||
| - needs to design database structure | ||
| - can handle more complex situations | ||
| {{< /columns >}} | ||
|
|
||
| Imagine we have 2 different files: `student_info` and `grade_record` | ||
|
|
||
|  | ||
|
|
||
| Notice the duplication among the 2 files. | ||
| This will waste storage if using a normal file system. | ||
| There may also be inconsistencies between the 2 files if only 1 is changed. | ||
| DBMS can control all of these things for you. | ||
|
|
||
|  | ||
|  | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,166 @@ | ||
| --- | ||
| title: "CS134-lecture-20210602" | ||
| # date: 2021-06-02T16:16:01-07:00 | ||
| draft: false | ||
| bookToc: true | ||
| tags: ["DBMS", "ER model"] | ||
| --- | ||
|
|
||
| ## DBMS cont. | ||
|
|
||
| ### Database users | ||
|
|
||
|  | ||
|
|
||
| If we're storing student information in a database, we'll have fields such as | ||
|
|
||
| - age | ||
| - birthdate | ||
|
|
||
| If we want to store one in the database, which should we pick? | ||
| Why only one? | ||
|
|
||
| We should choose the birthdate because | ||
| - we can derive the age | ||
| - birthdate is also more accurate of a measure of age | ||
| - we won't need to increment the age in the database every year | ||
|
|
||
| What is the disadvantage of saving both? | ||
| - we don't want to waste space when we can derive the age from the birthdate. | ||
| - if we save both we have to make sure they are consistent. | ||
| In other words: we would have to increment the age on the birthdate. | ||
|
|
||
| For end users: | ||
| - casual end users: need to use a sophisticated database query language, like SQL | ||
| - naive users: use a menu-driven interface | ||
| - sophisticated end users: familiar with DBMS to implement their applications | ||
|
|
||
| ### Data models | ||
|
|
||
|  | ||
|
|
||
| High level models | ||
| - ER, entity-relationship model, best for relational database | ||
| - UML | ||
|
|
||
| Representational / implementation model | ||
| - relational data model, uses relational database | ||
| - object data model, O-O, O-R | ||
| - network and hierarchical model, uses graph model | ||
|
|
||
| ### DBMS architecture and data independency | ||
|
|
||
|  | ||
|
|
||
| At the conceptual schema level, the user doesn't necessarily know the exact implementation of the internal schema level. | ||
|
|
||
| ### Database languages | ||
|
|
||
|  | ||
|
|
||
| SQL is a comprehensive integrated language of DDL and DML for relational databases. | ||
|
|
||
| ## Entity-relationship model | ||
|
|
||
|  | ||
|
|
||
| {{< hint info >}} | ||
| Note: ER diagram notation can change based on different textbooks. | ||
| We will use the original notation that is used in our text book. | ||
| {{< /hint >}} | ||
|
|
||
| ### Entity and attributes | ||
|
|
||
|  | ||
|
|
||
| Properties can be used to describe the entity. | ||
| For example for a student: | ||
|
|
||
|  | ||
|  | ||
|  | ||
|  | ||
|
|
||
| On notation: | ||
| - entities are in rectangles | ||
| - attributes are circled and connected to the entity | ||
|
|
||
|  | ||
|
|
||
| The divisibility of an attribute depends on application. | ||
| We can divide address into subparts: | ||
|
|
||
|  | ||
|
|
||
| Here, address is the composite attribute. | ||
| Name can also be composite. | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
| Students can only have 1 birthdate, but they can have multiple phone numbers. | ||
| We can indicate that by a double circle. | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
| Since age can be calculated from the birthdate, we can put the age attribute in the ER diagram, but we indicate it can be derived with a dashed line. | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
| ### ER diagram notation | ||
|
|
||
|  | ||
|
|
||
| ### Keys | ||
|
|
||
|  | ||
|
|
||
| - must be a unique identifier | ||
|
|
||
| We underline the attribute name to indicate that it is the key | ||
|
|
||
|  | ||
|
|
||
| If we have an entity called classroom: | ||
|
|
||
|  | ||
|
|
||
| We can use a composite key of the attributes building and roomNo. | ||
|
|
||
|  | ||
|
|
||
| Keys must be minimal. | ||
| In other words: adding capacity to the composite key for the classroom model wouldn't add anything beneficial. | ||
|
|
||
| ### Value sets | ||
|
|
||
|  | ||
|
|
||
| ### ER diagram example | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ### Relationship | ||
|
|
||
|  | ||
|
|
||
| Relationships are drawn using a diamond. | ||
|
|
||
|  | ||
|  | ||
|  | ||
|
|
||
| ### Structure constraint | ||
|
|
||
|  | ||
|  | ||
|  | ||
|  | ||
|  | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,88 @@ | ||
| --- | ||
| title: "CS134-lecture-20210603" | ||
| # date: 2021-06-03T16:27:55-07:00 | ||
| draft: false | ||
| bookToc: true | ||
| tags: ["ER model"] | ||
| --- | ||
|
|
||
| ## ER model cont. | ||
|
|
||
| ### Structure constraint cont. | ||
|
|
||
|  | ||
|  | ||
|  | ||
|  | ||
|
|
||
| The reason we have both {{<k>}} M {{</k>}} and {{<k>}} N {{</k>}} is because they are are both in the same association. | ||
| It is okay to reuse {{<k>}} M {{</k>}} in other places in the diagram. | ||
|
|
||
|  | ||
|  | ||
|  | ||
|
|
||
| {{< hint info >}} | ||
| Note: The double line from `employee` to `works_for` indicates the total participation. | ||
| {{< /hint >}} | ||
|
|
||
| ### Weak entity | ||
|
|
||
|  | ||
|
|
||
| Entity has | ||
| - key | ||
| - instance | ||
|
|
||
|  | ||
|
|
||
| In this diagram, we don't necessarily know what key we should use for the `dependent` entity. | ||
| We need to treat `dependent` as a weak entity, indicated by a double box, also note the total participation association. | ||
|
|
||
|  | ||
|
|
||
| We can use a partial key of the `employee`'s key plus the `dependent`'s name, indicated by a dashed line. | ||
|
|
||
|  | ||
|
|
||
| ### Attributes of relationship types | ||
|
|
||
|  | ||
|  | ||
|  | ||
|
|
||
| {{< hint info >}} | ||
| Note: We could optionally have `mgr_start_date` belong to either entity, because it is a 1:1 relationship. | ||
| {{< /hint >}} | ||
|
|
||
| If one entity, say `department`, has total participation, it is better to have `mgm_start_date` belong to that entity. | ||
| (If we had `mgr_start_date` belong to `employee`, then all except 1 `employee`s would have a null attribute, thus it is better to have the `department` hold the attribute.) | ||
|
|
||
|  | ||
|
|
||
| We have 2 choices for the `emp_start_date` attribute, it can either belong to the `employee` or the `works_for` association. | ||
|
|
||
| ### Recursive relationships | ||
|
|
||
|  | ||
|
|
||
| ### Non-binary relationship | ||
|
|
||
|  | ||
|
|
||
| {{< hint danger >}} | ||
| Non-binary relationships will **not** be on exams/assignments. | ||
| {{< /hint >}} | ||
|
|
||
| ## A bigger ER diagram example | ||
|
|
||
|  | ||
|
|
||
| ## In class exercise | ||
|
|
||
| {{< hint info >}} | ||
| Note: This exercise is not included in the week 1 assignment. | ||
| {{< /hint >}} | ||
|
|
||
| 1. The university keeps track of each student's name (first name, middle name, last name), student number, social security number, permanent address and phone, birthdate, sex, class (e.g. freshman, sophomore, ..., graduate), and degree program (e.g. B.A., B.S., ..., Ph.D.). Some user applications need to refer to the street, city, state, and zip of the student's permanent address, and to the student's last name. Both social security number and student number have unique values for each student. | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| title: "CS134" | ||
| # date: 2021-05-14T18:39:36-07:00 | ||
| bookCollapseSection: true | ||
| weight: 1 | ||
| --- | ||
|
|
||
| # CS134 – Database Management Systems | ||
|
|
||
| {{<section>}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| title: "CS139" | ||
| # date: 2021-05-14T18:44:06-07:00 | ||
| bookCollapseSection: true | ||
| weight: 1 | ||
| --- | ||
|
|
||
| # CS139 – Operating System Principles | ||
|
|
||
| {{<section>}} |
Oops, something went wrong.