Hi there, Thanks for making Django a great framework for starters :D
Recently my team have run into problems when trying to remove a database column from the model without stopping our Django server, below is the timeline: 1. Before migration happens, we have column_A we want to remove, and running on old release_1 2. Now we run migration to remove column_A, our webserver is still running on old release_1 and serving requests 3. After migration, we ship the new release_2 However, between step 2 and 3, there are requests coming and referencing column_A we want to remove, and throws a exception of course. So is there anyway I can mark a database column a special state (deprecated, purged in memory, etc), so it has the following affect: 1. Won’t generate migration file, which means database wise, nothing has changed 2. However, when Django loads the model into memory, it will ignore column_A completely. So query, create, update, etc won’t try to access column_A. The reason we want to do it that way is so we can achieve no downtime, seamless migration for our application. I believe more people will benefit from this. Please let me know if more information is needed. Looking forward to hearing from you. Martin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/50dbe737-0b6c-42d2-9f76-99c188c916e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
