Data Structure and Database

[Kobe-DHVSU]

Let's work po sa structure of data ng system naten para concrete, useful, and organize yung data and info also yung database naten.

[Kobe-DHVSU]

Pa-work ng database and yung documentation (ERD and DFD), and here is the structure of data: === DATA ===

• Account

  • Id
  • Integer
  • Auto Increment
  • Primary Key
  • Name
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Username
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Unique data
  • Profile Image
  • VARCHAR(250) (String in PHP and will be use for file path)
  • Default value is "default-dp.jpg"
  • Email
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Unique data
  • Password
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Tokencode
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Type
  • Value neto either "user" or "admin" (gamit kayo ng ENUM)
  • Default value is "user"
  • Date Created
  • DateTime
  • Default value is Current_TimeStamp

• Game

  • Id
  • Integer
  • Auto Increment
  • Primary Key
  • Name
  • VARCHAR(250) (String in PHP)
  • Must not be null
  • Game Image
  • VARCHAR(250) (String in PHP and will be use for file path)
  • Default value is "default-game-icon.jpg"
  • Info
  • TEXT (varchar den pero with 65,535 characters)
  • Must not be null
  • Download Link
  • VARCHAR(250)
  • Must not be null
  • Date Added
  • DateTime
  • Default value is Current_TimeStamp

• Genre

  • Id
  • Integer
  • Auto Increment
  • Primary Key
  • Name
  • VARCHAR(250) (String in PHP)
  • Must not be null

• Game and Genre

  • Game Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Genre Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)

• Game Visited (Or Recent Game)

  • User Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Game Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Visited At
  • DateTime
  • Default value is Current_TimeStamp

• Favorite Games

  • User Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Game Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Date Added
  • DateTime
  • Default value is Current_TimeStamp
  • Yung mga foreign key lagyan nyo ng ON DELETE CASCADE para incase madelete yung game or user, yung data na to sa table na to maddelete den.

• User Response

  • Id
  • Integer
  • Auto Increment
  • Primary Key
  • Game Id
  • Integer
  • Foreign Key (On delete cascade)
  • User Id
  • Integer
  • Foreign Key (On delete cascade)
  • Rating
  • Integer (if keri i-limit from 1 - 5 lang yung value)
  • Must not be null
  • Comment
  • TEXT (varchar den pero with 65,535 characters)
  • Default value is null
  • Date Added
  • DateTime
  • Default value is Current_TimeStamp

• Logs

  • Id
  • Integer
  • Auto Increment
  • Primary Key
  • Account Id
  • Integer
  • Primary Key
  • Foreign Key (On delete cascade)
  • Activities of Users and Admins
  • VARCHAR(500) (String in PHP)
  • Must not be null
  • Date Added
  • DateTime
  • Default value is Current_TimeStamp

  Eto naman po yung Cardinalities and Relationships: === DATA RELATIONSHIP ===

• Game Visited (Many to Many, M:N)

  • User -> Games (one to many)
  • Game -> Users (one to many)

• Favorite Game (Many to Many, M:N)

  • User -> Games (one to many)
  • Game -> Users (one to many)

• Genre (Many to Many, M:N)

  • Game -> Genres (one to many)
  • Genre -> Games (one to many)

• Response (User and Response) (One to Many, 1:N)

  • User -> Responses (one to many)
  • Response -> User (one to one)

• Response (Game and Response) (One to Many, 1:N)

  • Game -> Responses (one to many)
  • Response -> Game (one to one)

• Log (One to Many, 1:N)

  • Account -> Logs (one to many)
  • Log -> Account (one to one)

  If may suggestions kayo sa mga details, please let me know so we can update these details before starting the database and documentation.