1.6

mssql-django 1.6 Release Notes (August 2025)

Feature:

• Django 5.1 Support (#452, #454, #456, #457)

  • What changed: Added comprehensive Django 5.1 compatibility including enhanced SQL compilation for empty order-by clauses, replaced deprecated index_together with Meta.indexes, enhanced sqlserver_mod() function, and removed deprecated fields
  • Who benefits: Django developers upgrading from 5.0 to 5.1, teams adopting modern Django patterns
  • Impact: Enables easy migration to Django 5.1

• Django 5.2 Support (#468, #460, #461)

  • What changed: Enhanced quote_name() method for schema.table format and table names with spaces, automatic test schema creation (inspectdb_special, inspectdb_pascal), added JSONArray function support
  • Who benefits: Django developers upgrading to 5.2, teams using complex database schemas with spaces in names
  • Impact: Enables easy migration to Django 5.2

Improvement:

• Enhanced JSON Functionality (#448, #459)

  • What changed: Improved JSON lookup logic for Django >=4.2 backward compatibility, refactored JSON has_key lookup implementation
  • Who benefits: Applications heavily using JSONField operations across different Django versions
  • Impact: Better performance and reliability for JSONField queries with backward compatibility

• Pipeline Infrastructure (#455, #446, #449, #451)

  • What changed: Added retry mechanism for dpkg lock errors, improved ODBC dependencies installation for Linux, excluded uncovered tests so pipelines are accurate.
  • Who benefits: Development teams & contributors
  • Impact: More reliable and stable build processes across different environments

Bug Fixes:

• Test Exclusions and Documentation (#469)

  • What changed: Fixed comprehensive test exclusions for Django 5.2 SQL Server limitations, updated README with detailed compatibility information
  • Who benefits: Developers evaluating Django 5.2 migration, teams running Django test suites
  • Impact: Clear visibility into supported features and known limitations, preventing unexpected test failures

• Circular Import Resolution (#453)

  • What changed: Fixed circular import issues in multiple database tests for Django 5.1
  • Who benefits: Applications using multiple database configurations
  • Impact: Eliminates import errors in multi-database Django