#34423: Migrations, UniqueConstraint lenght of identifier can be too long for
Postgres/MySQL
-------------------------------------+-------------------------------------
     Reporter:  Joel Shapiro         |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Migrations           |                  Version:  4.1
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  migrations,          |             Triage Stage:
  unique_constraint,                 |  Unreviewed
  UniqeConstraint                    |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Joel Shapiro):

 Replying to [comment:2 Mariusz Felisiak]:
 > Thanks for this ticket, however, I'm against this change. First of all
 it is backward incompatible. Constraints have been introduced in Django
 2.2 and constraints with a name of length greater than 63 characters are
 valid on other databases (64 on MySQL, 128 on MSSQL, etc.). I agree that
 it is a inconsistency between constraints and indexes policy but still we
 need to be careful with introducing incompatibilities. See also a related
 ticket, #30614.
 >
 > Please first start a discussion on the DevelopersMailingList, where
 you'll reach a wider audience and see what other think, and
 [https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
 tickets/#closing-tickets follow the triaging guidelines with regards to
 wontfix tickets].


 Thanks for the fast response!

 Yes, I agree. Not great to break compatibility.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34423#comment:3>
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/01070186fe75e7c5-c50a9989-d87d-4c83-8912-59e15de3bfc8-000000%40eu-central-1.amazonses.com.

Reply via email to