Re:Django and Postgres for the Busy Rails Developer
by Izkata on Thursday December 12, 2024 @03:13AM
(#42397274)
> - The makemigrations command to auto-generate pending migrations is very aggressive and will detect things as "changed" that don't impact the schema. If you changed some help text on a field, or a localization string, or the aforementioned only-in-python default value, makemigrations will see that as requiring a migration that does nothing. Leads to lots of cruft.
Don't know when this was added, I just quickly checked django 4.2
[ Parent
| on HN ]
Re:Django and Postgres for the Busy Rails Developer
by wfleming on Thursday December 12, 2024 @09:18AM
(#42399295)
Our Django app was still 1.x when I joined, I’ve gotten us up to 3.2 and hope to be on 4.0 in January. It looks like this was added in 4.1, so this’ll be a nice QOL improvement to look forward to, thanks.