Update Django model dasmon_statusvariable id field to bigint #165
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.
Short description of the changes:
Dasmon listener was not able to store updates from Dasmon because the table dasmon_statusvariable id field became out of range. The issue was fixed temporarily by making the integer type larger in the production database:
This changes the maximum ID's from 2147483647 to 9223372036854775807. See https://docs.djangoproject.com/en/3.2/ref/models/fields/#bigautofield
This PR is to make that change to the Django model as well so that the next time migrations are run on the database the Django model and database table definition are consistent.
Check list for the pull request
Check list for the reviewer
Manual test for the reviewer
References
Defect 5742