#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: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"636d701ded62807612df50da37fea3adb88a4bb6" 636d701]:
{{{
#!CommitTicketReference repository=""
revision="636d701ded62807612df50da37fea3adb88a4bb6"
[5.0.x] Fixed #35032 -- Corrected Char32UUIDField implementation in 5.0
release notes.
This fixes Char32UUIDField implementation in 5.0 release notes causing
records with UUIDFields created using pre-Django 5.0 and CHAR(32) not
being able to be saved anymore after upgrading and keeping the CHAR(32)
columns.
Regression in 7cd187a5ba58d7769039f487faeb9a5a2ff05540.
Backport of e72b2826ff1eaf2f48ee54a40d2f2988a1fdbb0a from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35032#comment:6>
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/0107018c67ab032a-e5c5f2b9-4735-4566-baf8-57071b9ee825-000000%40eu-central-1.amazonses.com.
