Re: Backward migration failing because of old dropped model

I have been a bit quick when I wrote that this finally works... Actually, with the dependency on 'form' app, I can now run my new migration for the 'billing' app and make it work backward as well. However my project's test suites won't run anymore, and fail with the same error as previously. I

Re: Backward migration failing because of old dropped model

Hello Maninder, Thanks for your answer, it's finally working now after adding a dependency to the initial migration file. See Bruckner's answer and my other reply for more details. Best regards, Adrien On Tuesday, January 21, 2020 at 9:19:24 AM UTC+1, maninder singh Kumar wrote: > > In your d

Re: Backward migration failing because of old dropped model

Hello Bruckner, Thank you for your answer. You pointed me in the right direction : the issue was with the Form model which is part of a custom app named 'form'... I've added a depency to the initial migration of the 'billing' app on the last current migration of 'form' app, and it solved the iss

Re: Backward migration failing because of old dropped model

In your database there is a table called django_migrations. Delete all references in it to any other migration than the initial one. [image: --] Maninder Kumar [image: http://]about.me/maninder.s.kumar On Tue, Jan 21, 2020 at 1:37 AM Adrien

Re: Backward migration failing because of old dropped model

Adrien, Your precise issue eludes me, but I have sometimes come across a similar issue when changing the field types of models.  It appears that you still have a reference somewhere in your code between the form and the model.  I suspect that form.Form.ticket_description is a Django default e