#33483: Index name migration instability between database engines
-------------------------------------+-------------------------------------
Reporter: Marti Raudsepp | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
oracle,migrations,indexes | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marti Raudsepp):
There is a simple work-around for this issue: explicitly specify index
names in models, e.g.
{{{
#!python
class Foo(models.Model):
...
class Meta:
indexes = [
models.Index(fields=['date_created'],
name='django_cele_date_cr_bd6c1d_idx'),
]
}}}
Opened a pull request for `django-celery-results`:
https://github.com/celery/django-celery-results/pull/283/files
--
Ticket URL: <https://code.djangoproject.com/ticket/33483#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/063.6bedff2f64bf02442eaf916a0d0c3309%40djangoproject.com.
