Opened 9 years ago
Closed 9 years ago
#24876 closed Uncategorized (duplicate)
Skipping migrations checking in sql* commands
| Reported by: | Marcin Nowak | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There are some IT projects that do not require Django`s builtin migrations but use external migration tool. As a maintainer of projects of that type I need to generate SQLs from models in same way as before Django 1.7.
Currently when I need to generate SQL for auth package using sql, sqlall and sqlindexes commands, I'm getting an error:
CommandError: App 'auth' has migrations. Only the sqlmigrate and sqlflush commands can be used when an app has migrations.
But I'm expecting generated SQL instead.
Please add possibility to generate SQL for smart users which know what they are doing.
I'm sending patch proposal as an attachment.
Please backport this fix to 1.7 and 1.8 branches.
Thank you very much.
Attachments (1)
Change History (2)
by , 9 years ago
| Attachment: | force-generating-sql.diff added |
|---|
comment:1 by , 9 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Duplicate of #24481. We'll need a new proposal for master as the affected sql* management commands have been removed there. A change is unlikely to be backported per our supported versions policy.
Patch proposal