Re: [Model, ORM] Disabling a field before actually removing it

For Info, the discussion on django-developers : https://groups.google.com/forum/#!topic/django-developers/Gr9x2OlWYN4 On Monday, June 24, 2019 at 3:01:55 PM UTC+2, Matthieu Rudelle wrote: > > From the tests we conducted, even fields that are nullable and that are > not used in the cod

Re: [Model, ORM] Disabling a field before actually removing it

ins that the table is missing with a 500. On Monday, June 24, 2019 at 2:20:38 PM UTC+2, Vinicius Assef wrote: > > I would, before everything, deploy code to stop using the field. > > After that, I would make it nullable and, then, remove it from the table. > > On Mon, 24 Jun 2019 at 05

Re: [Model, ORM] Disabling a field before actually removing it

+2, Aldian Fazrihady wrote: >>> >>> My solution to this problem was by adding more migrations steps: >>> 1. Step to make the field nullable. >>> 2. Backward step to fill value to the removed field. >>> 3. Step to remove the field. >>> >>&

Re: [Model, ORM] Disabling a field before actually removing it

o fill value to the removed field. > 3. Step to remove the field. > > Regards, > > Aldian Fazrihady > > > On Thu, 20 Jun 2019, 19:37 Matthieu Rudelle, > wrote: > >> Hi there! >> >> I am about to file a feature request but I figured this might have been &g

[Model, ORM] Disabling a field before actually removing it

Hi there! I am about to file a feature request but I figured this might have been discussed (although I can't find where). The use case is when removing fields in a production environment. We run our django migrations without downtimes, such that basically, from time to time we have an old