Fix: Resolve inconsistency in APIToken dialog_id field definition #5749
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.
The
dialog_id
field was inconsistently defined:migrate_db()
function, it was set tonull=True
.null=False
.This inconsistency caused an issue during the initial deployment where the database table did not allow
dialog_id
to be null. As a result, callingAPITokenService.save(**obj)
insystem_app.py
raised the following error:What problem does this PR solve?
Error: peewee.IntegrityError: null value in column "dialog_id" violates not-null constraint
Type of change