Bug #91699 | Contribution: Fix constraint introspection for table indices in Django | ||
---|---|---|---|
Submitted: | 18 Jul 2018 14:50 | Modified: | 10 May 2022 21:25 |
Reporter: | OCA Admin (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / Python | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[18 Jul 2018 14:50]
OCA Admin
[18 Jul 2018 14:50]
OCA Admin
Contribution submitted via Github - Fix constraint introspection for table indices in Django (*) Contribution by Dane Hillard (Github daneah, mysql-connector-python/pull/44#issuecomment-405952376): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_198845507.txt (text/plain), 1.79 KiB.
[18 Jul 2018 15:45]
MySQL Verification Team
Thank you for the contribution.
[10 May 2022 21:25]
Philip Olson
It appears this bug was lost and forgotten over time, which is unfortunate. The good news is the issue was fixed in 8.0.22; here's the related 8.0.22 release note: Added Django 3.0 support while preserving compatibility with Django 2.2. Removed support for Django 1.11 with Python 2.7. We're sorry for the delayed response; I believe the contribution process has improved since 2018 so hopefully this doesn't happen again. Thanks Dane for the contribution!