RELEASE: 1.7.2#528
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sumitmsft
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release 1.7.2
Bug Fixes
FIX: AttributeError on
.explain()for Django 4.0+ (FIX: AttributeError on .explain() for Django 4.0+ #524, closes explain_format missing in self.query causes django admin app to not work properly #409)Django 4.0 replaced
query.explain_format/query.explain_optionswithquery.explain_info. The compiler now reads the correct attributes based on Django version.FIX: DATETIMEOFFSET timezone support and
Now()withUSE_TZ=True(FIX: Updates TimeZone support for DATETIMEOFFSET type, fixes incorrect Now() in USE_TZ=True cases. #484, closes Datetime conversion issue with USE_TZ and settings.TIME_ZONE != 'UTC'? #371, closes Datetimeoffset support ? #136)handle_datetimeoffsetnow correctly parses the timezone offset from SQL Server binary data, returning timezone-aware datetimes forDATETIMEOFFSETcolumns.Now()now emitsSYSDATETIMEOFFSET()whenUSE_TZ=True, fixing incorrect timestamps on non-UTC SQL Server hosts.Maintenance
Test Improvements
FIX: Remove
returninfinallythat swallows exceptions (FIX: Remove return in finally that swallows exceptions (#417) #526, closes return in finally swallows exceptions #417)Test utility
_check_jsonfield_supported_sqlite()no longer silently swallowsBaseExceptionsubclasses.Added timezone offset tests: UTC, +05:30 (IST), -05:00 (EST), -09:30 (Marquesas), +05:45 (Nepal)
Added
NowSQLTemplateTestsverifyingSYSDATETIMEOFFSETvsSYSDATETIMEbased onUSE_TZAdded
ExplainRegressionTestsfor.explain()behavior