You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 8, 2019. It is now read-only.
Currently we have several ForeignKey constraints in the Location database object. It seems that it would make much more sense to have One-to-one constraints instead, and it would make much more sense to have these fields in the TrainStatus model itself as opposed to the Location model.
Acceptance Criteria
The TrainStatus model should contain the one-to-one constraints for platform, location, etc (As required).
Change TrainStatus Database Model
Currently we have several ForeignKey constraints in the Location database object. It seems that it would make much more sense to have One-to-one constraints instead, and it would make much more sense to have these fields in the TrainStatus model itself as opposed to the Location model.
Acceptance Criteria
The TrainStatus model should contain the one-to-one constraints for platform, location, etc (As required).