Re: [Feature Request][Model, ORM] Disabling a field before removal to support continuous delivery

2019-06-29 Thread 'Matthieu Rudelle' via Django developers (Contributions to Django itself)
-fields > > On Monday, June 24, 2019 at 3:15:04 PM UTC+2, Matthieu Rudelle wrote: >> >> Hi there, >> >> I can't find any previous ticket proposing a solution to this problem so >> here are my findings: >> >> **Use case**: >> When using contin

Re: [Feature Request][Model, ORM] Disabling a field before removal to support continuous delivery

2019-06-26 Thread 'Matthieu Rudelle' via Django developers (Contributions to Django itself)
Does that sound like feature-request material? It seems to me django is the good place to add this flexibility as it has exclusive access to the underlying DB. On Tue, Jun 25, 2019 at 9:08 AM Matthieu Rudelle wrote: > How does the "safe" field of migrations work with other migra

Re: [Feature Request][Model, ORM] Disabling a field before removal to support continuous delivery

2019-06-25 Thread Matthieu Rudelle
> then make migration, then apply this changes to your environment - you will > get same issue. So to automate deployment process and to get achievable > result you want I think you need something more complex: deploying atomic > changes, but for me it sounds more about deployment

[Feature Request][Model, ORM] Disabling a field before removal to support continuous delivery

2019-06-24 Thread Matthieu Rudelle
Hi there, I can't find any previous ticket proposing a solution to this problem so here are my findings: **Use case**: When using continuous delivery several versions of the code can be running in parallel on se same DB. Say for instance that release 2.42 is in production, 2.43 is about to b