$ the-wire · showcase
DJANGO FIXES NULL TIME FIELD HANDLING IN GEOSPATIAL MAPPING
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
LayerMapping now correctly reads null time fields after a follow-up alignment with OFTDate and OFTDateTime value properties.
Jacob Walls landed a fix for issue #37242 that resolves incorrect handling of null time fields in Django's LayerMapping geospatial utility [1]. The patch brings the `OFTTime` implementation into alignment with existing `value` properties on `OFTDate` and `OFTDateTime` [2], ensuring consistent null handling across temporal field types. This follow-up to an earlier commit addresses a gap that could cause silent data corruption or unexpected behavior when processing geospatial datasets with missing time values. The fix is targeted but important for anyone using GeoDjango's OGR layer mapping functionality with nullable time columns.
Action items
- → Verify LayerMapping usage with null time fields in your geospatial models django/django [plan]
- → Monitor main branch for the next Django release containing this fix django/django [monitor]
References
- [1] Fixed #37242 -- Fixed reading null time fields in LayerMapping. ↗ django/django
- [2] Fixed #37242 -- Fixed reading null time fields in LayerMapping. ↗ django/django