tegrate with the migration
> framework, rather than anything more complicated.
>
> Tom
>
> On 23 Dec 2020 at 17:32:23, Ryan Hiebert wrote:
>
>> This is an interesting discussion that is separate from, but related to,
>> django-safemigrate, which we use to separate which mi
Want to share lib I work previously for migration safety with postgres some
time ago: https://github.com/tbicr/django-pg-zero-downtime-migrations there
are also checker and replacement of unsafe mirations with safe replacement.
ср, 23 дек. 2020 г. в 12:18, Adam Johnson :
> Hi Tom,
>
> I love this
there are similar to `alter table drop column` issue: `alter table rename
column`, `drop table`, `rename table`. (honestly `alter table drop column`
and `drop table` a bit different wiith `alter table remane column` and
`rename table`)
Look like you general flow for migration:
1. change code
Just short hint about git blame.
Github has functionality to get more deep git blame:
https://help.github.com/en/articles/tracking-changes-in-a-file, more over
pycharm has similar functionality too (potentially another editors and IDE
have too). I suggest that git blame is more tooling issue, not
