Fix #864: ComplexDateTimeField should fall back to None when null=True
This commit is contained in:
		
				
					committed by
					
						 David Bordeynik
						David Bordeynik
					
				
			
			
				
	
			
			
			
						parent
						
							baf79dda21
						
					
				
				
					commit
					ce9d0d7e82
				
			| @@ -5,6 +5,7 @@ Changelog | ||||
|  | ||||
| Changes in 0.9.X - DEV | ||||
| ====================== | ||||
| - ComplexDateTimeField should fall back to None when null=True #864 | ||||
| - Request Support for $min, $max Field update operators #863 | ||||
| - `BaseDict` does not follow `setdefault` #866 | ||||
| - Add support for $type operator # 766 | ||||
| @@ -76,7 +77,6 @@ Changes in 0.9.X - DEV | ||||
| - Make `in_bulk()` respect `no_dereference()` #775 | ||||
| - Handle None from model __str__; Fixes #753 #754 | ||||
|  | ||||
|  | ||||
| Changes in 0.8.7 | ||||
| ================ | ||||
| - Calling reload on deleted / nonexistent documents raises DoesNotExist (#538) | ||||
|   | ||||
		Reference in New Issue
	
	Block a user