Released: SQL Server 3rd Party Backend for Django v1.1

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

We have released version 1.1 of the SQL Server 3rd Party Backend for Django. This release contains support for the upcoming release of Django 4.0, as well as a number of issue fixes.

 

Our plan is to time releases to coincide with major releases of Django and SQL Server, to ensure users of this project can keep up to date with Django while continuing to use SQL Server as a backend.

 

Notable changes include:

  • Added core support for Django 4.0
  • Added ActiveDirectoryMsi authentication
  • Fixed bulk_update issue when exceeding limit for number of parameters

For the full history of release changes and fixes, please see the Release Notes wiki.

 

To use this backend for Django 4.0, no changes are required to your existing Django project settings - provided it is already configured for MSSQL (see project README). One recommendation is to ensure the USE_TZ option is set to False. This project does not yet support this option, so this should be explicitly disabled in the settings.py file:

 

 

DATABASES = {
...
}

# set this to False if the backend does not support using time zones
USE_TZ = False

 

 

If you encounter any issues or have any feedback, head over to our mssql-django project repository and submit an issue.

 

Happy Coding,

Team Microsoft

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.