#33507: Use native UUID data type on MariaDB 10.7+
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: raydeal
Type: New feature | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: mariadb | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Klaas van Schelven):
I just ran into this [https://github.com/bugsink/bugsink/issues/226 here].
Caused by not carefully reading the release notes, but quite hard to
debug.
Having actually read those notes now, I'm left to wonder:
1. what will happen with existing databases that are from a post-5.0
world? They will have been created with uuid columns. Will the suggested
migration path accidentally brake _those_?
2. the suggested path is "varchars everywhere". But my project is deployed
on many DB backends, also postgres. So the suggested solution is a
downgrade for those and or create the risk of breakage on those...
I realise these questions may be "more on me than on Django" but OTOH the
present issue seems like exactly the spot where people with such problems
would gather.
--
Ticket URL: <https://code.djangoproject.com/ticket/33507#comment:22>
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 visit
https://groups.google.com/d/msgid/django-updates/01070199c473bc1d-d2615375-3d7f-4a9c-aa76-d7cda1e3fd5b-000000%40eu-central-1.amazonses.com.
