Reverting didn't see to do anything but I'll spread around some breakpoints
in 3.1 and 3.2 and compare what happens.
I have another project, on 3.0, that I'm testing with 3.2 with the exact
same naming scheme (except every app has a a label in their AppConfig, in
the one that fails, not all of
I came across this today:
https://code.djangoproject.com/ticket/31300
This is essential for my domain. I understand this is a big-ticket change
but there is no good workaround for it. One could use a Model method but
this sticks everything into the application layer instead. If done directly
Hi All,
We've released the preview version 1.0b1 of the Microsoft SQL Server 3rd
Party Backend for Django. This version supports Django 2.2, 3.0 and 3.1.
What's coming up next between now and GA release? We are re-adding optional
regex support, so that the regex DLL file is downloadable from
*phew* old cruft indeed. I wasn't using the AppConfigs I *thought* I
was using so no wonder things were flaky.
It might for paranoia's sake be worth mentioning in the upgrade notes
for 3.2 that if you get NodeNotFoundError when running
migrations/database tests on 3.2 to double check the app
