#33982: TypeError creating DB table SQL with ExclusionConstraint as Statement
returned instead of str
-------------------------------------+-------------------------------------
Reporter: James Beith | Owner: James
| Beith
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | 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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"7ba9a448316de976735c1b14d069ed033ebed6ea" 7ba9a448]:
{{{
#!CommitTicketReference repository=""
revision="7ba9a448316de976735c1b14d069ed033ebed6ea"
[4.1.x] Fixed #33982 -- Fixed migrations crash when adding model with
ExclusionConstraint.
Regression in 0e656c02fe945389246f0c08f51c6db4a0849bd2.
Backport of 19e838daa8872ee29fbea0bc471c2a6443f26835 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33982#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/0107018316cff1f0-4e3de9a6-498d-4dd5-a3b7-1923bfa6ca68-000000%40eu-central-1.amazonses.com.
