Added a check to deactivate AlterIndexTogether if the Oracle database is used. This should, according to #732 fix the migration issue with Oracle, but have no database to check with. So supposedly resolves #732.
This commit is contained in:
parent
faacf58f56
commit
2130522559
1 changed files with 6 additions and 0 deletions
|
|
@ -2,6 +2,7 @@
|
|||
from __future__ import unicode_literals
|
||||
|
||||
from django.db import models, migrations
|
||||
from django.conf import settings
|
||||
import evennia.utils.picklefield
|
||||
|
||||
|
||||
|
|
@ -53,3 +54,8 @@ class Migration(migrations.Migration):
|
|||
index_together=set([('db_key', 'db_category', 'db_tagtype')]),
|
||||
),
|
||||
]
|
||||
# if we are using Oracle, we need to remove the AlterIndexTogether operation
|
||||
# since Oracle seems to create its own index already at AlterUniqueTogether, meaning
|
||||
# there is a conflict (see issue #732).
|
||||
if settings.DATABASES['default']['ENGINE'] == "django.db.backends.oracle":
|
||||
del operations[3]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue