#31731: Dead code in the sequence_reset_sql for postgres and oracle
-------------------------------------+-------------------------------------
Reporter: axil | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: sql sequence reset | Triage Stage: Accepted
postgres oracle |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
This should likely be included in the same PR that tackles #31730 and move
the sequence identification logic to the command.
--
Ticket URL: <https://code.djangoproject.com/ticket/31731#comment:2>
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.7786c0d2b333a04b3f3d24acb8ee7487%40djangoproject.com.