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
The Operation model has a foreign key relationship with the Operator, but the OperationDesignatedOperatorTimeline table also maintains a relationship between Operation and Operator. This creates redundancy and confusion when determining the current operator assigned to an operation, as there are two potential sources of truth.
We need to discuss:
The purpose and necessity of both relationships.
How to handle cases where these relationships might conflict.
Whether we should refactor to rely on one source of truth and its potential impact on the codebase.
The feasibility of maintaining the current setup with clear guidelines to reduce confusion.
This discussion aims to identify the best approach to ensure clarity and consistency in the relationship between Operation and Operator.
The text was updated successfully, but these errors were encountered:
Describe the task
The Operation model has a foreign key relationship with the Operator, but the
OperationDesignatedOperatorTimeline
table also maintains a relationship between Operation and Operator. This creates redundancy and confusion when determining the current operator assigned to an operation, as there are two potential sources of truth.We need to discuss:
Whether we should refactor to rely on one source of truth and its potential impact on the codebase.
The text was updated successfully, but these errors were encountered: