AzureFeeds

We are happy to announce the release of mssql-django 1.7.3.

This release improves SQL Server connection compatibility for modern authentication scenarios and fixes a subclassing edge case in backend server-property caching.

Highlights

1) Authentication parsing and connection string handling improvements

We fixed how extra_params authentication settings are interpreted and now parse ODBC-style key/value segments more robustly.

What changed:

• Authentication mode is parsed from extra_params using a spec-aligned parser.


• Trusted_Connection and SSPI injection now respects explicit Authentication= modes.


• Password injection behavior is driven by authentication mode, so password-based modes still receive PWD correctly.


• Parser behavior is hardened for cases like braced values, embedded semicolons, escaped braces, whitespace, and empty values.

Why it matters:

• Prevents invalid combinations such as appending Trusted_Connection=yes when an explicit authentication mode is provided.


• Avoids ODBC driver failures (including FA001) in authentication flows such as ActiveDirectoryIntegrated.


• Improves predictability for advanced connection-string configurations.

2) Server-property cache fix for DatabaseWrapper subclasses

We fixed a KeyError when subclassing DatabaseWrapper and accessing server-property cached values.

What changed:

• Replaced mutable default-argument cache patterns with explicit class-level cache dictionaries.


• Added regression coverage for subclass access paths.

Why it matters:

• Custom backend wrapper subclasses now behave correctly when reading cached server properties.


• Prevents runtime failures in extensibility scenarios.

Upgrade

If you are building an application that uses Entra authentication, you’ll want this as your minimum version.

Compatibility

1.7.3 continues the same compatibility range introduced in 1.7.x:

• Django 3.2 through 6.0


• Python 3.8 through 3.14


• All supported versions of Microsoft SQL

Thank You

Thank you to everyone who reported issues, validated fixes, and contributed improvements.

As always, please open an issue if you hit regressions or have connection/authentication scenarios you want us to look into.