Hello Sylvain, I think you have two concerns here,
On Friday, December 9, 2016 at 1:39:50 PM UTC-5, Sylvain Dégué wrote: > SO im thinking about reset completly my production database and remove all > the migrations to start fresh. I dont have much data in the production > database so its probably the best time. > > Is there any drawback to flushing the database and removing the migrations > files What is impact of removing migrations? The migrations store information about how you changed your database schema over time. If this historical information is un-necessary for you, then there's no point in having it around. What is impact of flushing the database? This is something only you can answer - we have no knowledge of your business, and only you will know how best to support your customers. But since we are talking about a production database, might I offer an alternative? Take a backup of your database and store it somewhere. You don't need to keep it running, but having it around might be useful later on. Yours, Abraham V. -- You received this message because you are subscribed to the Google Groups "Django users" 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]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0218756e-00b4-46ab-9eea-e1f01b491117%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
