#22611: sqlclear command tries to drop non-existing constraint with ForeignKey
to
self (postgresql)
-------------------------------------+-------------------------------------
Reporter: valberg | Owner: valberg
Type: Bug | Status: assigned
Component: Core (Management | Version:
commands) | 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by andrewgodwin):
* severity: Normal => Release blocker
Comment:
I'd actually like to drop the sql* commands for apps that are marked as
having migrations, as they're no longer needed, and we'll finally
deprecate and remove them along with other creation-based stuff in 2.0
(they should pretty much be replaced by sqlmigrate, which obviously stays)
In particular, I think that:
* sql
* sqlall
* sqlcustom
* sqlindexes
* sqldropindexes
* sqlsequencereset
should be modified to error and quit if supplied with an app that's got
migrations. This would leave just `sqlflush` and `sqlmigrate` working for
those apps, which both make sense in the context.
--
Ticket URL: <https://code.djangoproject.com/ticket/22611#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 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/065.8e4f7aea1a21664f799c7acfa61cd031%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
