The mxODBC Django Database Engine™ product allows you to easily connect your Django website to just about any database backend on the market today, giving you the reliability of the commercially supported eGenix.com product mxODBC and the flexibility of the ODBC standard as middle-tier architecture.
With the mxODBC Django Database Engine 1.2, you receive two ways to connect to your databases:
mxODBC Django Database Engine works on Windows, Linux, Mac OS X and FreeBSD, providing you with the same consistent interface, flexibility and robustness across all of these platforms.
ORM support for more database backends will follow in future releases. If you're interested in a particular backend, please let us know and we can adjust the priorities.
The mxODBC Django Database Engine includes all software needed to connect Django to an ODBC manager. However, it does not include an ODBC manager or any ODBC drivers. You have to have these installed in order to be able to use the mxODBC Django Database Engine.
On Windows, the situation is very simple: most databases come with ODBC drivers and register them with the Windows ODBC manager that's part of every Windows system.
Please consult the ODBC driver documentation for details on how to setup ODBC data sources. The mxODBC Django Database Engine Administration and User Manual also includes a section on this topic and some helpful hints in case you run into problems.
On Unix, you will have to install one of the popular ODBC managers iODBC, unixODBC or DataDirect and then register the ODBC drivers for your database with these ODBC managers.
Linux systems usually come with at least one of these ODBC managers preinstalled. Please see the mxODBC Django Database Engine Administration and User Manual for setup instructions.
On Mac OS X, you can use the system system ODBC manager (which actually is a version of the popular iODBC manager). If this is not installed on your system, you can download it from Apple or use the alternative ODBC Manager which is maintained by Actual Technologies.
Please see the mxODBC Django Database Engine Administration and User Manual for setup instructions.
The mxODBC Django Database Engine product is a commercial product and made available under the terms and conditions of the eGenix.com Commercial License Agreement, Version 1.3.0 (PDF file).
When purchasing a license for the mxODBC Django Database Engine product, you will receive a digitally signed Proof of Authorization authorizing you to install the product for use within one Django Project Installation, i.e. a Django installation running a single site project.
If you are using Django clusters or multiple Django site projects on a single machine, you will have to buy one Django Project license per Django site project that you want to use the engine with.
If you would like to evaluate the mxODBC Django Database Engine, please request an evaluation license online or send an email to the eGenix.com Sales Team and include the following information: name of the licensee, number of evaluation licenses.
We will then send you the requested number of evaluation licenses. The evaluation licenses have a built-in timeout of 30 days, but are otherwise fully functional.
If you are satisfied with the product, you can then proceed to the next section.
Production licenses for the mxODBC Django Database Engine product can be bought via our secure eGenix.com Online Shop which is hosted by ShareIT.com (a service of Digital River). Licenses are sold per Django Project Installation. For quotes on prices, volume discounts, site and corporate licenses please write to sales@egenix.com.
After purchase, you will receive the necessary license files from eGenix.com within two business by email to the address you specified in the ordering process.
If you need to buy licenses for third parties (e.g. as contractor), please consult sales@egenix.com for instructions.
If you have questions about the ordering process, or the needed number of licenses, please write to the eGenix.com Sales Team.
The documentation for the mxODBC Django Database Engine and the underlying mxODBC is available in form of PDF files:
mxODBC Django Database Engine Administration and User Manual - HTML and PDF
This manual includes instructions on how to install, configure and use the mxODBC Django Database Engine.
mxODBC Reference Manual - HTML and PDF
The PDF files are also available as part of the installation in theThe mxODBC Reference describes the included eGenix.com product mxODBC which is used by the mxODBC Django Database Engine to interface to the various database backends.
Please note that the mxODBC package included in the mxODBC Django Database Engine can only be used from within Django and is usually a different version than the stand-alone mxODBC package.
mxodbc_django/
directory.
A successful installation of mxODBC Django Database Engine requires these two steps:
Redistribution of these files is not allowed. Please contact the eGenix Sales Team for details about redistribution possibilities and terms.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
The Windows ODBC manager which comes with the Windows Operating
System will be used by this distribution. On 64-bit Windows versions,
the 32-bit variant of the ODBC manager will be used.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
The 64-bit variant of the Windows ODBC manager which comes with the Windows Operating System will be used by this distribution.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
You will need to have one of popular ODBC managers for Unix installed on the target system: iODBC 3.52.x or unixODBC 2.3.x. We have successfully tested the mxODBC Django Database Engine with iODBC 3.52.7 and unixODBC 2.3.1. The DataDirect ODBC manager is also supported.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
You will need to have one of popular ODBC managers for Unix installed on the target system: iODBC 3.52.x or unixODBC 2.3.x.
We have successfully tested the mxODBC Django Database Engine with
iODBC 3.52.7 and unixODBC 2.3.1. The DataDirect ODBC manager is also
supported.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
Note that Mac OS X comes with a UCS2 build of Python, so please try the UCS2 product versions first.
Mac OS X ships with the iODBC ODBC manager as system default ODBC manager. Please configure your data sources using the system ODBC manager.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
Note that Mac OS X comes with a UCS2 build of Python, so please try the UCS2 product versions first.
Mac OS X ships with the iODBC ODBC manager as system default ODBC manager. Please configure your data sources using the system ODBC manager.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
You will need to have one of popular ODBC managers for Unix installed on the target system: iODBC 3.52.x or unixODBC 2.3.x. We have successfully tested the mxODBC Django Database Engine with iODBC 3.52.7 and unixODBC 2.3.1.
For instructions on how to install the egg archives, please see the installation section below.
These archives include the mxODBC Django Database Engine and all necessary eGenix.com mx Products (including mxODBC) prebuilt for Django installations in one binary archive.
You will need to have one of popular ODBC managers for Unix installed on the target system: iODBC 3.52.x or unixODBC 2.3.x. We have successfully tested the mxODBC Django Database Engine with iODBC 3.52.7 and unixODBC 2.3.1.
For instructions on how to install the egg archives, please see the installation section below.
Solaris and AIX binaries can be made available on demand.
mxODBC Django Database Engine is a commercial product for which we don't distribute the source code.
If you have requirements for other platforms or Django versions, please send us a note. The mxODBC Django Database Engine will compile on most Unix-like platforms where iODBC and/or unixODBC are available.
We can also prepare special versions which link directly against the database ODBC drivers. This may in some cases give you access to more advanced native database features.
On Unix it is important to know whether you need to download a distribution for a narrow Unicode build of Python (UCS2) or a wide version (UCS4).
Most Unixes ship with wide UCS4 Python builds these days (including RedHat and SuSE). In order to make sure, please run the following command which will tell you what kind of Python installation you have:
bin/python -c "import sys;print(sys.maxunicode<66000)and'UCS2'or'UCS4'"
If you get errors such as "unresolved symbol PyUnicodeUCS2_AsEncodedString" when trying to load an extension from the distribution, you have likely installed an archive for a wrong Unicode version.
The egg archives we provide are made available through two PyPI-style indexes which the egg tools setuptools/easy_install/pip/zc.buildout can access to automatically download and install the right egg archive.
There are two indexes, one for Python UCS2 builds:
https://downloads.egenix.com/python/index/ucs2/
and one for Python UCS4 builds:
https://downloads.egenix.com/python/index/ucs4/
If you are using a Python UCS2 build, then you can install the egg archives using this command:
easy_install -i https://downloads.egenix.com/python/index/ucs2/ \
egenix-mxodbc-django
For UCS4 builds, please use this command:
easy_install -i https://downloads.egenix.com/python/index/ucs4/ \
egenix-mxodbc-django
The command line parameters for other tools such as pip are similar. Please consult their documentation for details.
In some cases, easy_install and other download tools cannot map the platform name to the name used in the egg archive. If you get errors during the installation, please manually download the right egg archive and then run the command directly on the downloaded egg archive:
easy_install \
egenix_mxodbc_django-1.2.0-py2.7-linux-x86_64.egg
The mxODBC Django Database Engine User Manual has the details on how to install and setup the package.
We provide several different installation variants based on setuptools/distribute's easy_install, zc.buildout, the pip package manager, distutils compatible prebuilt archives and MSI installers for Windows.
eGenix offers these support options:
Professional level support for this product as well as all other eGenix products and Python itself is available directly from the developers at eGenix.com.
eGenix.com offers professional consulting services for all questions and tasks around this product, including customized modifications, help with integration and on-site problem solving. Please contact sales@egenix.com for details.
In order for our users to keep in touch and be able to help themselves, we have created the egenix-users user mailing list.
Version 1.2.0 is the first public release. Versions 1.0 and 1.1 were eGenix internal releases supporting earlier Django versions.