Changes between Version 4 and Version 5 of P5


Ignore:
Timestamp:
04/07/26 22:37:30 (6 days ago)
Author:
211099
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • P5

    v4 v5  
    7171Every column in the database holds just one value, so there are no lists or multi-value attributes in the cells. There are no repeating columns, each table has a primary key, and all attributes are atomic, so my relations satisfy 1NF.
    7272
     73=== 2NF Check
     74Every table that has a simple (non-composite) primary key is already in 2NF, so we only need to check the tables that have composite keys.
     75STATUS {story_id, status} → There are no other attributes, so it satisfies 2NF.
     76CONTENT_TYPE {notification_id, content_type} → There are no other attributes, so it satisfies 2NF.
     77SUGGESTION_TYPE {suggestion_id, suggestion_type} → There are no other attributes, so it satisfies 2NF.
     78LIKES {user_id, story_id} → like_created_at depends on {user_id, story_id} together, so it satisfies 2NF.
     79COLLABORATION {user_id, story_id} → collab_created_at depends on {user_id, story_id} together, so it satisfies 2NF.
     80ROLES {user_id, story_id, roles} → There are no other attributes, so it satisfies 2NF.
     81PERMISSION_LEVEL {user_id, story_id, permission_level} → There are no other attributes, so it satisfies 2NF.
     82HAS_GENRE {story_id, genre_id} → There are no other attributes, so it satisfies 2NF.
     83READING_LIST_ITEMS {list_id, story_id} → added_at depends on {list_id, story_id} together, so it satisfies 2NF.
     84NOTIFY {user_id, story_id, notification_id} → There are no other attributes, so it satisfies 2NF.
     85NEED_APPROVAL {suggestion_id, story_id, chapter_id} → There are no other attributes, so it satisfies 2NF.
     86Since there are no partial dependencies in any of the tables, this schema satisfies 2NF.