it 240 final project

Update:

Insert:

Delete:

Data manipulation of unstructured data can lead to inconsistencies called data anomalies. Inconsistencies are common in related tables where the main table, called parent table, has a dependent reference table, called child table. There are three data anomalies that I will address: insertion anomaly, modification anomaly, and deletion anomaly. Insertion anomaly occurs when a new record is added to a child table but whose record does not exist in its referenced parent table. Deletion anomaly occurs when a record in the parent table is deleted without its related records in the referenced child tables. As such, both insertion anomalies and deletion anomalies result in orphan child tables. On the other hand, modification anomaly can occur when updating records in a database. Records can be updated in a main table but leave out the referenced tables and vice versa. Comment by Evelyn Lulis: This is in the general; you need to address your specific data as we did in class

B. Examples of the current approach

The current approach involves entry of data in spreadsheets using Microsoft Excel. Workbooks exist that contain various worksheets of data. The data is organized in tables and columns that describe the rows of data inserted. Information stored include biodata of the players, matches, and individual player performance. Comment by Evelyn Lulis: You need sample data so can address the issues n parts 2a and 2c

C. The new approach Comment by Evelyn Lulis: This belongs in Part 2 when you normalize the data. You might be able to extract the info you need to address the Update/Insert/Delete issues.

Update:

Insert:

Delete:

My approach will make use of integrity constraints to guarantee accuracy, consistency, and validity of data stored. Integrity constraints utilized in the Hawkins Soccer Club database include the following: required data, attribute domain constraints, multiplicity, entity integrity, referential integrity, and general constraints. Required data constraint is a type of integrity constraint suitably applied on attributes whose fields must hold valid values but never contain null values. Attribute domain constraint is a type of integrity constraint ideally enforced on attributes that should only accept defined set of values. For example, a marital status attribute can be set to accept either single or married as the only valid values. Multiplicity constraint is a type of integrity constraint defined on specific relationships that exist between data in a relational database. It is commonly applied in a one-to-many relationship. For example, a soccer team can have many players, but a soccer player can be legally signed to only one soccer team. As such, multiplicity constraint would ensure that no soccer player exists in more than one soccer team. Entity integrity is a type of integrity constraint that is enforced on primary keys of attributes to ensure that they hold valid values which must be unique always. It also ensures that primary key attribute fields do not hold null values. Referential integrity constraint is defined on two related tables. If a foreign key in the first table references a primary key in the second table, then each value of the foreign key in the first table must either be available in the second table or be null. This ensures that no orphan records exist, that is, records existing in the first table with a foreign key that does not match a primary key in the second table. The first table is thus considered the child table while the referenced table is referred to as the parent table. Finally, general constraint is a type of integrity constraints that limits permissible range of values to be entered in an attribute field. Comment by Evelyn Lulis: No pronouns