Thanks Michael. It has been interesting so far and I'm looking forward to
understanding what I've done😄
Original message From: Michael MacIntosh
Date: 19/12/19 06:58 (GMT+10:00) To:
django-users@googlegroups.com Subject: Re: Renaming sequences Hey Mike,I'm
ango users
Subject: Re: Renaming sequences Why you did
taht on production and not to try before recreate the db in other placeOn Wed,
18 Dec 2019, 20:59 Michael MacIntosh, wrote:Hey
Mike,
I'm not sure about your specific setup, but I assume you are using the
django.contrib.auth user model an
at your user models and any
> custom authorization / authentication happens in there.
>
> Hope that helps!
>
> Cheers,
> Michael.
>
> On 12/17/2019 10:26 PM, Mike Dewhirst wrote:
> > Are there any consequences for renaming sequences to match the tables
> > which o
thing containing
auth, like "catapp_auth" so it is clear that your user models and any
custom authorization / authentication happens in there.
Hope that helps!
Cheers,
Michael.
On 12/17/2019 10:26 PM, Mike Dewhirst wrote:
Are there any consequences for renaming sequences to match th
Are there any consequences for renaming sequences to match the tables
which own them?
In an existing production Django project I have just converted auth.user
into common.user and company.userprofile into common.userprofile.
Having gone through the migration process more or less unscathed
5 matches
Mail list logo