Annikka/evennia
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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.

Browse source
This commit is contained in:
Griatch 2015-11-18 00:11:33 +01:00
parent faacf58f56
commit 2130522559
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
evennia/typeclasses/migrations/0001_initial.py
View file

@ -2,6 +2,7 @@
from __future__ import unicode_literals from __future__ import unicode_literals
from django.db import models, migrations from django.db import models, migrations
from django.conf import settings
import evennia.utils.picklefield import evennia.utils.picklefield
@ -53,3 +54,8 @@ class Migration(migrations.Migration):
index_together=set([('db_key', 'db_category', 'db_tagtype')]), 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]