Open evanhsu opened 8 years ago
If the 'helicopters' dB table is changed to be more generic then any resource type could be accommodated.
Rename the helicopters
table to vehicles
.
Add a vehicles.type
column.
Rename the tailnumber
column to designator
.
Rename the model
column to description
.
Add a capabilities
column.
Then the Helicopter class can be changed to a polymorphic Vehicle class.
Add a crews.vehicle_type
column.
Vehicle designators would need to stop enforcing uniqueness at the database level. Uniqueness would need to be enforced for designators only within each vehicle_type (and enforce uniqueness only within each crew for Fire Engines, since there's a lot of duplicates nationwide).
Extend this site to handle other resource types:
Each resource type will need their own version of the "Status Update" page. Implementation should include a new Class for each resource type, for example: