# Database Schema:

[TahjDev]

• [ ] Contains correct datatypes
• [x] Contains appropriate constraints/details
  • [x] primary key
  • [x] not null
  • [x] unique
  • [x] indexed
  • [x] foreign key
• [x] Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
• [x] foreign key and table name are lowercased, snake_cased and back_ticked
• [x] Correctly formatted
  • [x] schema is written in a table format
  • [x] the table's name are lowercased, snake_cased and back_ticked
  • [x] the table header column names are bolded
  • [x] columns names are lowercased and snaked_cased and back_ticked

[TahjDev]

• Why does a user have an account_id and then accounts has an account_owner_id wouldn't that be enough for the association. An account belongs to a user?
• Should the data entry in the dates table be not null
• What is the board_comissions entry relate to, the data type is an integer, is it how many people have permission
• should the status entry in the status table not have the not null constraints

[YWBK]

• Points above addressed as discussed
• Revised the incorrect data types.
• Additionally, added array data types to Workspaces to keep track of ordering of its Boards, to Boards to keep track of ordering of its Columns and Groups, and to Groups to keep track of ordering of its Items
• Additionally, changed item_persons, statuses, and dates to have cell_id columns rather than item_id column, because a single item can have multiple columns of the same type.