#30595: sqlsequencereset should inform that no sequences found.
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Management | Version: master
commands) |
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 felixxm):
* stage: Unreviewed => Accepted
* version: 2.2 => master
* type: New feature => Cleanup/optimization
* easy: 0 => 1
Comment:
Thanks for the report. I don't think that `sqlsequencereset` should raise
`CommandError`, but I agree that we can add an extra output if we don't
find any sequences, e.g.
{{{#!python
if not statements and self.verbosity >= 1:
self.stdout.write('No sequences found.')
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30595#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.efd62ed679699cc86405955f435013ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
