We need a method of storing the history of the tasks and boards as per
"
Back-end (40%)
The second part of the project assessment evaluate the back-end functionality of the application. At least the following functionality should be provided:
User accounts.
The ability to store user interactions and the results of those interactions.
The ability to search previous user interactions.
"
Proposal
Two tables, one for tasks and one mapping their history. Alternatively a boolean that describes whether it is the Head version could be used, while an iteration number is used to preserve order. An example of the latter is provided.
Tasks:
id
board
OP
title
message
tags
urgency
color
etc.
HEAD
iteration
int
FK(int)
FK(int)
string(50?)
string(5000?)?
enum options
enum options
enum options
...
boolean
int
Another method could be to simply search through the iteration number for the most recent task, however a HEAD boolean may or may not be simpler.
Regardless of the tracking method, we will likely require a Tasks table to provide task functionality to the boards.
Brief
We need a method of storing the history of the tasks and boards as per " Back-end (40%) The second part of the project assessment evaluate the back-end functionality of the application. At least the following functionality should be provided:
"
Proposal
Two tables, one for tasks and one mapping their history. Alternatively a boolean that describes whether it is the Head version could be used, while an iteration number is used to preserve order. An example of the latter is provided.
Tasks:
Another method could be to simply search through the iteration number for the most recent task, however a HEAD boolean may or may not be simpler.
Regardless of the tracking method, we will likely require a Tasks table to provide task functionality to the boards.