From 78211b13a51f2ada1c7beb81ff97ef11f9e239eb Mon Sep 17 00:00:00 2001
From: Simon Charette <charette.s@gmail.com>
Date: Mon, 3 Mar 2014 20:12:42 -0500
Subject: [1.7.x] Fixed #12030 -- Validate integer field range at the model
 level.

Thanks to @timgraham for the review.

Backport of 1506c71a95 from master
---
 docs/releases/1.7.txt | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'docs')

diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 18b9234ab9..5dd4500026 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -678,6 +678,11 @@ Models
   Previously this used to work if the field accepted integers as input as it
   took the primary key.
 
+* Integer fields are now validated against database backend specific min and
+  max values based on their :meth:`internal_type <django.db.models.Field.get_internal_type>`.
+  Previously model field validation didn't prevent values out of their associated
+  column data type range from being saved resulting in an integrity error.
+
 Signals
 ^^^^^^^
 
-- 
cgit v1.3