#31730: manage.py sqlsequencereset not implemented for sqlite3
-------------------------------------+-------------------------------------
Reporter: axil | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: sql sequence reset | Triage Stage: Accepted
sqlite3 |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by axil):
The main question for me here is whether or not should
`sequence_reset_sql` automatically cascade to the autocreated many-to-many
tables. From its main use cases described in #31731 (and considering that
de facto this feature does not work right now and noone is reporting any
problems) it looks as if it shouldn't.
--
Ticket URL: <https://code.djangoproject.com/ticket/31730#comment:6>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.443192eba29e5bf192a7590f73600775%40djangoproject.com.
