One more note... I deleted the database and migrations and started clean
again, and this time when I opened the migration file it had
setting.AUTH_USER_MODEL the way I wanted it. So I don't know why it didn't
do that before.
On Monday, October 11, 2021 at 9:17:39 AM UTC-4 bnmng wrote:
> That'
That's genius, David. Thank you!
On Sunday, October 10, 2021 at 5:56:07 PM UTC-4 David Nugent wrote:
> Why not just edit the migration file directly and substitute 'my_custom..'
> for settings.AUTH_USER_MODEL?
>
> There should be no problem in doing that.
>
> Regards, David
>
> On Sun, Oct 10,
Why not just edit the migration file directly and substitute 'my_custom..'
for settings.AUTH_USER_MODEL?
There should be no problem in doing that.
Regards, David
On Sun, Oct 10, 2021 at 3:02 AM bnmng wrote:
> Django "strongly recommends" you create custom user, and in your apps you
> can refer
I agree
Le sam. 9 oct. 2021 à 16:02, bnmng a écrit :
> Django "strongly recommends" you create custom user, and in your apps you
> can refer to the custom user with "settings.AUTH_USER_MODEL" or with
> get_user_model().
>
> Here's the problem. If you develop an app which refers to the custom
>
4 matches
Mail list logo
