Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"a357c854c91b513e3713f2eb72e9742d49c2e701"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a357c854c91b513e3713f2eb72e9742d49c2e701"
 [1.6.x] Fixed #16992 -- Added InnoDB warning regarding reuse of
 AUTO_INCREMENT values.

 Thanks kent at nsc.liu.se for the report.

 Backport of c54fa1a7bc 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/073.6330e71dc68d69b2c88e34b9fcca955e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"37587624bf79490e97da1bd04547cdce8b77b9fb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="37587624bf79490e97da1bd04547cdce8b77b9fb"
 [1.5.x] Fixed #16992 -- Added InnoDB warning regarding reuse of
 AUTO_INCREMENT values.

 Thanks kent at nsc.liu.se for the report.

 Backport of c54fa1a7bc 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/073.09f03d62541974f65a80bb1f07ef5189%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

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


Comment:

 Fixed in c54fa1a7bc365fec79d4971bf22d5ad2799fde67.

-- 
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/073.c62ac39390072a95de3bf8070a2352bf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by timo):

 Sounds good. I'd add it after "It's probably the best choice at this
 point."
 {{{
 However, note that the the InnoDB autoincrement counter is lost on a MySQL
 restart because it does not remember the ``AUTO_INCREMENT`` value, instead
 recreating it as "max(id)+1". This may result in an inadvertent reuse of
 :class:`~django.db.models.AutoField` values.
 }}}

-- 
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/073.c1e4bb2fcf0259a7d6c1c83bd5f3f828%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by kedmiston):

 Considering adding the following to the Databases.txt:

 "InnoDB autoincrement counter is lost on a MySQL restart because it does
 not remember the AUTO_INCREMENT value, instead recreating it as
 "max(id)+1". This may result in an inadvertant reuse of a previous value."

-- 
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/073.adfa593e48b549275ba447a54d8dbfcd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  kedmiston
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by kedmiston):

 * status:  new => assigned
 * owner:  nobody => kedmiston


-- 
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/073.a3f651362f5d9ba5f278a422f44ae349%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
--+
 Reporter:  kent@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timo):

 It looks like this is the MySQL ticket for this issue:
 http://bugs.mysql.com/bug.php?id=199

-- 
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/073.7424fa759a1a4d2b3f48006b05da55c3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
--+
 Reporter:  kent@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by akaariai):

 * easy:  0 => 1


Comment:

 Adding a docs note about this should be easy to do.

-- 
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/073.d11483c3e4ce4ec65d324bb92e5473f4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
--+
 Reporter:  kent@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 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
--+

Comment (by ramiro):

 See also #16961 for a related MySQL particularity regarding
 `AUTO_INCREMENT`.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
--+
 Reporter:  kent@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 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 aaugustin):

 * component:  Database layer (models, ORM) => Documentation
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 The MySQL devs say:
 > This behavior is a documented feature which will be fixed in the future
 at the same time a fast COUNT(*) is introduced to InnoDB.

 That was in 2003; I'm not holding my breath. And I don't think we have to
 document every bug in MySQL.

 That said, since it was decided for #10164 to enforce non-reusable primary
 keys, in this case, it's worth adding a paragraph to the MySQL notes.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)

[Django]

#16992: MySQL InnoDB AUTO_INCREMENT bug (next value to use forgotten at restart)
-+-
 Reporter:  kent@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by ramiro):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 #10164 reports similar behavior with sqlite3, but it is controllable with
 DDL by adding a `' AUTOINCREMENT'` suffix to the !AutoField's  DB field
 creation code.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.