#29641: Add support for unique constraints to Meta.constraints
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Ian Foote
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"dba4a634ba999bf376caee193b3378bc0b730bd4" dba4a63]:
{{{
#!CommitTicketReference repository=""
revision="dba4a634ba999bf376caee193b3378bc0b730bd4"
Refs #29641 -- Refactored database schema constraint creation.
Added a test for constraint names in the database.
Updated SQLite introspection to use sqlparse to allow reading the
constraint name for table check and unique constraints.
Co-authored-by: Ian Foote <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29641#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ee9e8cc40e7348388ba3b5e3a267449f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
