Database - Revision history

Aesetholephews: /* Useful Wikipedia Pages */

2023-02-14T01:28:39Z

Useful Wikipedia Pages

2023-02-14T01:28:22Z

Useful Wikipedia Pages

2023-02-14T00:47:40Z

Useful Wikipedia Pages

2023-02-09T23:22:16Z

Database Basic

2023-02-09T23:18:19Z

Working Prototype

2023-02-09T23:15:34Z

Working Prototype

2023-02-09T23:03:22Z

Working Prototype

2023-02-09T23:01:59Z

Working Prototype

2023-02-09T22:45:05Z

Working Prototype

2023-02-09T22:44:59Z

Working Prototype

@@ Line 7: / Line 7: @@
 *Databases can be indexed to streamline queries.
-=Useful Wikipedia Pages=
+=Useful Resources=
 *[https://en.wikipedia.org/wiki/Relation_(database) Relation]
 *[https://en.wikipedia.org/wiki/Database_normalization#Satisfying_EKNF Database Normalization w/ step by step instructions w/ examples]

@@ Line 15: / Line 15: @@
 *[https://en.wikipedia.org/wiki/Relational_database Relational Database, lengthy overview]
 *[https://rstsaygili.medium.com/many-to-many-relationships-in-relational-databases-af867547914f Resolving Many-To-Many Relationships]
 =Working Prototype=

@@ Line 14: / Line 14: @@
 *[https://en.wikipedia.org/wiki/Database_index Database Indexing]
 *[https://en.wikipedia.org/wiki/Relational_database Relational Database, lengthy overview]
 =Working Prototype=

@@ Line 1: / Line 1: @@
-=Database Basic=
+=Database Basics=
 *Relational databases (e.g. MySQL) are probably the most common. Essentially they store data in a set of 2D tables (relations) that follow certain rules of normalization and can be linked to each other via relational algebra (mostly set theory type functions).
 *To address problems encountered when trying to interface a RDBMS with an object-oriented programming language, alternative non-relational database structures (e.g. XML, NoSQL, Hierarchical, Network) are available and may have advantages in certain situations.

@@ Line 48: / Line 48: @@
 Each primary key (disease) can be associated with multiple values in each attribute. For example, CAD is associated with multiple risk factors (age, male gender, smoking, etc) and multiple symptoms (angina, dyspnea, nausea, etc). At the same time, each of these risk factors and symptoms are associated with other diseases besides CAD. For example, smoking is a risk factor for CAD, lung cancer, PVD, COPD, head and neck cancer, etc. In order to handle this many-to-many cardinality of the data, multiple base tables should be created and an associative table (junction table) can then be created as needed. The base tables in the above example would be:
-{| class "wikitable"
+{| class="wikitable"
 |+ Base Table 1
+|-
-! Disease (PK)
+| Disease (PK)
 |-
 | Risk factors
 |}
 Disease < Symptom < Disease

@@ Line 45: / Line 45: @@
 |-
 | Studies || text || M2M
 |}
 Disease < Symptom < Disease

@@ Line 26: / Line 26: @@
 ! Attribute !! Domain !! Cardinality
 |-
-| Disease (PK) || text || M2M
+| Disease (PK) || text || --
 |-
 | Risk factors || text || M2M