Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"581b9e504752840fd7716e44c5c30292636355a4" 581b9e5]:
 {{{
 #!CommitTicketReference repository=""
 revision="581b9e504752840fd7716e44c5c30292636355a4"
 [1.8.x] Fixed #25767 -- Fixed data truncation possibility with
 Positive(Small)IntegerField on MySQL.

 Backport of 710e11d076b9e5ef3e3b486dfb70bb55b788691c from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.dda9c54b7e17d866208c82bfae069b60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"11d54e8f0da96d355b8dff17af8d5aa6bb3386db" 11d54e8f]:
 {{{
 #!CommitTicketReference repository=""
 revision="11d54e8f0da96d355b8dff17af8d5aa6bb3386db"
 [1.9.x] Fixed #25767 -- Fixed data truncation possibility with
 Positive(Small)IntegerField on MySQL.

 Backport of 710e11d076b9e5ef3e3b486dfb70bb55b788691c from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.927fa6eafc9500b2984cc1036d0520fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"710e11d076b9e5ef3e3b486dfb70bb55b788691c" 710e11d0]:
 {{{
 #!CommitTicketReference repository=""
 revision="710e11d076b9e5ef3e3b486dfb70bb55b788691c"
 Fixed #25767 -- Fixed data truncation possibility with
 Positive(Small)IntegerField on MySQL.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.fddf5774eda76fe328e30b7d0c2e8fbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by georgemarshall):

 The CI server seems to have crashed out, needs to be rerun.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.d411d16265bf32458085dac090327edc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 Tests aren't passing on the [https://github.com/django/django/pull/5674
 pull request] and I left some comments for improvement.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.3c558d824468fa2bc6306cd2727859bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by georgemarshall:

Old description:

> The integer ranges for `PositiveSmallIntegerField` and
> `PositiveIntegerField` are reflective of `UNSIGNED INT` and `UNSIGNED
> BIGINT`. When the ORM actually uses `UNSIGNED SMALLINT` and `UNSIGNED
> INT` when creating these fields.
>
> The side effect of this is that data will pass validation checks, but
> fail to commit to the database.

New description:

 The integer ranges for `PositiveSmallIntegerField` and
 `PositiveIntegerField` are reflective of `UNSIGNED INT` and `UNSIGNED
 BIGINT`. When the ORM actually uses `UNSIGNED SMALLINT` and `UNSIGNED INT`
 when creating these fields.

 The side effect of this is that data will pass validation checks, but will
 be munged by the database.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.4f2ec66d3f170a1221a51c148d6eba70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charettes (added)


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.0fe03444865384e2b1c53e3e1d232db9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Unreviewed => Accepted


Comment:

 Since this a bug in a new feature (introduced in 1.8) that can possibly
 lead to data loss I think this is worth a backport.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.7298c81e37986def723298c76532dd42%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by georgemarshall):

 * owner:  nobody => georgemarshall
 * status:  new => assigned
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.afdebc694b44c3152d8d33be4c4427a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25767: integer_field_ranges are incorrect for MySQL backend

[Django]

#25767: integer_field_ranges are incorrect for MySQL backend
--+
 Reporter:  georgemarshall|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The integer ranges for `PositiveSmallIntegerField` and
 `PositiveIntegerField` are reflective of `UNSIGNED INT` and `UNSIGNED
 BIGINT`. When the ORM actually uses `UNSIGNED SMALLINT` and `UNSIGNED INT`
 when creating these fields.

 The side effect of this is that data will pass validation checks, but fail
 to commit to the database.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/057.408317b4726acd261d4ce21d6edbc94a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.