django 1.8 The SchemaEditorClass is None

[jbrissier]

I try to use django-pyodbc with django 1.7 / 1.8 but i always get the following error:

'The SchemaEditorClass attribute of this database wrapper is still None')
NotImplementedError: The SchemaEditorClass attribute of this database wrapper is still None

My environment:
Django (1.8.11)
django-pyodbc (0.3.0)
pip (7.1.2)
pyodbc (3.0.10)
setuptools (18.2)
wheel (0.24.0)
python 2.7.11

Are migrations supported? Should i disabled them?

[individual-it]

same problem here, any solutions?

[dulabs]

bump! +1

[mikeyu96]

• 1

[microcomet]

same problem, is this a bug or something wrong in my settings?
My settings:

'dev': {
        'ENGINE': "django_pyodbc",
        'HOST': "xxxxxxxxx,1433",
        'USER': "xxx",
        'PASSWORD': "xxxx",
        'NAME': "dev_wfan",
        'OPTIONS': {
            'driver': 'ODBC Driver 13 for SQL Server',
            'dsn': 'self_mssql',
            'host_is_server': True
        },
    },

[shadiakiki1986]

Any solutions yet?

EDIT: According to this, with django 1.11 (and even 1.10), the repository to use is django-pyodbc-azure. And if the error Previous SQL was not a query appears on initial migration, check issue 64

[RossRogers]

Unfortunately, not at this time due to contributors being slammed.

…

On Tue, Oct 3, 2017 at 3:18 AM, Shadi Akiki ***@***.***> wrote: Any solutions yet? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#110 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD_flI4Vyr_tmBuY7YJ9xGZEbUVTip7Oks5sogoOgaJpZM4H8lyA> .

[RossRogers]

This issue is resolved on the trunk and in alpha release 2.0.0a1, using Django 2.0. I am closing this issue, but if this is an unacceptable outcome, please re-open the ticket. If you require this to be backported to the django-1 branch then please feel free to re-open this ticket. Unfortunately, it is likely to remain unresolved, as there may not be any takers on this backporting task. Apologies.

[brianedelman]

Unfortunately this is still an issue for me with 2.0.0a1 using Django 2.0.2 as well.