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

1.5

mssql-django 1.5 Release Notes (April 2024)

Added:

• Add flag to db_comments condition (#373)
  • Users can now set the supports_comments feature to false to disable comment retrieval

Fixed:

• Fix add autofield (#357)
• Fix param format bug (#378)
• Fix query, ensure that we only check tables in the right schema (#381)

1.4.2

mssql-django 1.4.2 Release Notes (March 2024)

Fixed:

• restore original uuid behaviour (#364)
  Will be adding native UUID support in future release

1.4.1

mssql-django 1.4.1 Release Notes (March 2024)

Added:

• add support for boolean aggregates (#332)
• Support GeneratedField (#335)
• Native support for UUID (From Char(32) to uniqueidentifier) (#329)

Fixed:

• revert can_return_rows_from_bulk_insert to False (#336)
• Modify bulk update default value (#341)
• Remove subqueries from group by. Fixes #343 (#344)
• Set boolean expr flag to false, unskip constraint tests (#349)
• Fix aggregate queries with case expressions (#354)
• Update SQL query for split parameters function (#358)

1.4

mssql-django 1.4 Release Notes (January 2024)

Added:

• Add db_comment support (#318)
• Django 5.0 support (#327)

Fixed:

• Fix introspection test on SmallAutoField (#287)
• Fix converting date/time from character string. (#290)
• Add logic to include deleting _meta.indexes to _delete_indexes (#292)
• Implement fix for empty aggregate (#324)

1.3

mssql-django 1.3 Release Notes (May 2023)

Added:

• Add case-sensitive feature for Replace function (#222)
• Add support for Django 4.2 (#269)

Fixed:

• Fix #196: changed getting system datetime to cached_property (#217)
• Fix an issue of adding OFFSET keyword for legacy SQL Server versions (#218)
• Fix left padding function to return strings with correct length (#226)
• Fix limit_offset_sql to handle cases when there is no OFFSET (#235)

1.2

mssql-django 1.2 Release Notes (December 2022)

Added:

• Timezone support (To use will need to do some manual migrations. See the wiki page on timezone support) (#140, #160)
• Fixed inserting into tables with triggers fails (#158, #161)
• Returning rows after bulk insert is off by default and can be enabled by setting return_rows_bulk_insert in the OPTIONS dictionary to True (#161)
• Add capability to convert to and from AutoField and BigAutoField (#128)
• Added hashing function support (#152)
• Add xor bit shift support (#172)
• Add support for left and right arithmetic bit shift (#182)
• Add jsonfield support for sql managed instance (#198)
• Add support for sql server 2022 (#202)
• Add support for django 4.1 (#208)

Fixed:

• Fix #137: handle legacy unique together constraint (#138)
• Fix random order by issue (#142)
• Fix altering unique, nullable field to non-nullable error (#163)
• Fix date_trunc_sql() to work with < 4-digit year (#188)

1.1.3

mssql-django 1.1.3 Release Notes (April 2022)

Added:

• Add possibility for token authentication (#102)
• Returning ids/rows after bulk insert (#107)
• Unit test for issues #110 and #90 (#115)

Fixed:

• Only drop necessary indexes during field rename (#97)
• KeyTransformExact applied to all databases (#98)
• Alter nullability for foreign key (#93)
• Overridden functions not working with other DBs (#105)
• reset_sequences argument in sql_flush (#112)
• Add offset clause for all Django versions (#117)
• Fixed issues related to unique constraints (#106)

1.1.2

Fixed:

• Duplicated index created when alter foreignkey
• Migration error when alter fields to JSONField/TextField
• Migration not detected for non-default schema
• Unique index lost when renaming M2M field

1.1.1

Fixed:

• Migration alterfield and indexes issue

Added:

• setencoding and setdecoding in settings.py