pybase | basic python utilities | Code Analyzer library

Currently (May 2020) the python module ibm_db_django may exhibit issues with Django versions above 2.0.0. Some of the issues have workarounds, others do not.

At the present date, the ibm_db_django readme page on github states: "Django Framework Minimum 1.7.x and Maximum 2.0"

You write that your Django version is v3 which may not yet be fully supported by ibm_db_django, although workarounds are possible in many cases, even to allow the initial manage.py migrate to succeed with Db2-LUW at least. But other issues exist, so it may be wise to stay with the supported (tested) Django max release 2.0.0.

This situation may change when developers release newer versions of ibm_db_django. Please refer to the github issues page.

If you change your Django version, it is wise to make a new project (django-admin startproject), and merge your changes into its settings.py file.

Otherwise the previous settings.py may cause the new Django version to throw exceptions.

I choose to use a virtualenv in Python (via virtualenvwrapper-win) but although this is recommended, it is not essential.

On Microsoft-Windows10 x64 1909, the following combination results in successful manage.py migrate(although the metadata will be in the default database, which may not be what you want):

• python 3.7.7 (64-bit)

• pip 20.1.1

• Django 2.0.0 ( <= 2.2.12 works for initial migration).

• ibm-db 3.0.1

• ibm-db-django 1.2.0.0a0

To install a specific version x.y.z of a moduleName, first uninstall any existing version, then use the python -m pip install moduleName==x.y.z

For my settings.py I apply these changes: