FIX: Test Exclusions for 5.2 & update README #469
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request expands support for newer Django versions (5.1 and 5.2) in the MSSQL-Django backend, documents version-specific limitations, and updates the test exclusion list to reflect new incompatibilities and areas for community contribution. The README is updated to clarify the level of support and known issues for each Django version, while
testapp/settings.py
now programmatically excludes failing tests based on Django version.Django version support and documentation:
Test suite management:
testapp/settings.py
introduces version-aware exclusions for tests that fail due to SQL Server limitations in Django 5.0, 5.1, and 5.2. This includes tuple lookups, multi-column foreign keys, JSONField operations, and composite primary key features. [1] [2]Community contribution guidance: