Changes between Initial Version and Version 2 of Ticket #30614


Ignore:
Timestamp:
Jul 5, 2019, 5:18:57 AM (5 years ago)
Author:
Mariusz Felisiak
Comment:

After double-thinking I'm not sure if we want this change. First of all it is backward incompatible and it is not a minor incompatibility. Constraints have been introduced in Django 2.2 and for all databases (except Oracle) names starting with an underscore _ or a digit, or with a name of length greater than 30 characters are valid (63 characters on PostgreSQL, 64 on MySQL). I agree that it is a inconsistency between constraints and indexes policy but still we need to be careful with introducing incompatibilities.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30614

    • Property Has patch set
    • Property Owner changed from nobody to Can Sarıgöl
    • Property Status new → assigned

  • Ticket #30614 – Description

    initial v2  
     1Constraints names cannot start with an underscore or a number and cannot be longer than 30 characters on Oracle. We can restrict them with system checks for cross-database compatibility.
Back to Top