#30670: Document SchemaEditor.add_constraint()/remove_constraint() methods.
-------------------------------------+-------------------------------------
     Reporter:  akash1997            |                    Owner:  akash1997
         Type:                       |                   Status:  assigned
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  2.2
     Severity:  Normal               |               Resolution:
     Keywords:  SchemaEditor,        |             Triage Stage:  Accepted
  unique_together, constraints       |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by akash1997):

 Replying to [comment:2 felixxm]:
 > `SchemaEditor` supports `add_constraint()` and `remove_constraint()`
 operations for
 [https://docs.djangoproject.com/en/2.2/ref/models/constraints/
 Meta.constraints] manipulation.

 I just went through the code for
 
[https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L347
 add constraint] and
 
[https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L353
 delete constraint] in schema editor and the comment in the function says
 that it adds/deletes a check constraint. What about unique together
 constraint?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30670#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/067.146b12896e3395f7246f3e7cec0b3df0%40djangoproject.com.

Reply via email to