#30595: sqlsequencereset should inform that no sequences found.
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
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
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
One problem I foresee with outputting a message when no sequences are
found is that it could break scripts piping the output into a SQL shell or
simply expecting STDOUT to be valid SQL. I guess we could output an SQL
comment of the form `-- No sequences found` or use STDERR instead?
Also I don't see why `sqlsequencereset` is special with regards to other
`sql*` commands that also have the same behavior; it should either not be
changed or changed for all commands `sql*` commands to be coherent.
--
Ticket URL: <https://code.djangoproject.com/ticket/30595#comment:3>
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.5bd218cc4396d1a7a7cb769bf9d58e97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
