#35032: Cannot save record with UUID field after migrating existing UUIDField
created in Django < 5.0
-------------------------------------+-------------------------------------
Reporter: Emanuel Andrecut | Owner: Emanuel
| Andrecut
Type: Bug | Status: assigned
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: uuid, mariadb, | Triage Stage: Ready for
UUIDField, DataError | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* owner: nobody => Emanuel Andrecut
* status: new => assigned
* has_patch: 0 => 1
* stage: Accepted => Ready for checkin
Comment:
Replying to [comment:3 Emanuel Andrecut]:
> I've dropped the Django changes in the PR and updated class
Char32UUIDField in release notes, please check.
Looks good, thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/35032#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c67726680-b6325fb1-fdd6-42cb-9648-12c0da44c38b-000000%40eu-central-1.amazonses.com.
