Fix/realtime django models tripupdates vehiclepositions alerts subissue 13 #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g gtfs-realtime-bindings
…hiclePositions, and Alerts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update to Sub-issue #13 — Model Constraints and Temporal Integrity
Additional constraints and validation rules were incorporated into the
TripUpdate,StopTimeUpdate, andVehiclePositionmodels to strengthen data integrity.These changes introduce new
CheckConstraintdefinitions and database indexes to enforce temporal consistency, prevent invalid timestamp sequences, and ensure that all stored values remain within valid ranges.The added constraints improve reliability across the Realtime ingestion pipeline and reduce the risk of inconsistent or malformed GTFS-Realtime data entering the system. This completes the requirements for Sub-issue #13.