Re: [PATCH 2/4] migrations: 0043_merge_patch_submission: do less work

On Sat, 2021-07-17 at 03:19 +1000, Daniel Axtens wrote: > - we do a lot of legwork to prevent there being a column with the same >name in a base class and subclass. This is purely for django's benefit >as databases don't see the class relationship and handle column names >being the

Re: [PATCH 2/4] migrations: 0043_merge_patch_submission: do less work

Stewart Smith writes: > On Jul 16, 2021, at 10:20 AM, Daniel Axtens wrote: >> >>  - we do a lot of legwork to prevent there being a column with the same >> name in a base class and subclass. This is purely for django's benefit >> as databases don't see the class relationship and handle

Re: [PATCH 2/4] migrations: 0043_merge_patch_submission: do less work

On Jul 16, 2021, at 10:20 AM, Daniel Axtens wrote: > >  - we do a lot of legwork to prevent there being a column with the same > name in a base class and subclass. This is purely for django's benefit > as databases don't see the class relationship and handle column names > being the same

[PATCH 2/4] migrations: 0043_merge_patch_submission: do less work

- we do a lot of legwork to prevent there being a column with the same name in a base class and subclass. This is purely for django's benefit as databases don't see the class relationship and handle column names being the same across tables just fine. Unfortunately renaming columns in