Indeed, David is right. The --update flag is intended for developing a
feature branch and adding extra changes to a work-in-progress migration.
This is why it requires the migration to not be applied.
On Sun, Apr 9, 2023 at 9:20 PM David Wobrock
wrote:
> Hi,
>
> As you can see, the error
Hi,
As you can see, the error message seems quite clear:
> Cannot update applied migration 'authentication.0001_initial'.
One cannot edit a migration that has already been applied.
To update it, you can undo it by running "migrate authentication zero" and
then run "makemigrations --update" again.
Do you need that '--update' parameter?
On Fri, 7 Apr 2023 at 05:57, Saifullah Shahen wrote:
> in my custom user model, initially, my model looks like this
>
> class User(AbstractUser, BaseModelWithUUID):
> phone = models.CharField(max_length=11,
> validators=[validate_phone_number])
> I do
Please follow https://docs.djangoproject.com/en/4.1/topics/auth/customizing/
On Fri, Apr 7, 2023 at 3:27 AM Saifullah Shahen
wrote:
> in my custom user model, initially, my model looks like this
>
> class User(AbstractUser, BaseModelWithUUID):
> phone = models.CharField(max_length=11,
>
