﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
24481	Improve sqlmigrate to be more flexible and allow bypassing migrations on disk	pascal chambon		"
When upgrading a django+djangocms install to latest versions, things got broken (at least one sql table with missing, even though MIGRATION_MODULES was well filled and ""manage.py migrate"" indicated all was up-to-date).

I wanted to use sqlall and other commands to diff my existing DB with the ""theoretical"" one, but django refused, indicating that only sqlmigrate and sqlflush were allowed for apps with migrations. I had to redeploy another install from scratch to do the diff.

Wouldn't it be better to issue a warning in these cases, but let the developper use these tools to understand what's wrong, and manually ""fake"" migrations when stuffs are out of control ?"	New feature	new	Core (Management commands)	dev	Normal		migrate migrations sqlall		Accepted	0	0	0	0	0	0
