diff options
| author | Simon Charette <charette.s@gmail.com> | 2014-03-03 20:12:42 -0500 |
|---|---|---|
| committer | Simon Charette <charette.s@gmail.com> | 2014-03-25 14:31:54 -0400 |
| commit | 78211b13a51f2ada1c7beb81ff97ef11f9e239eb (patch) | |
| tree | 2bd0dd1116c06a3705f423d278ee8bf723128995 /docs | |
| parent | 7eaf329ad38ff7ea6b47f1b0a3c20ca7a5ad079b (diff) | |
[1.7.x] Fixed #12030 -- Validate integer field range at the model level.
Thanks to @timgraham for the review.
Backport of 1506c71a95 from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.7.txt | 5 |
1 files changed, 5 insertions, 0 deletions
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 ^^^^^^^ |
