Re: [Django] #33576: InconsistentMigrationHistory when multiple projects with custom user models share the same database. (was: CustomUser: InconsistentMigrationHistory in multiple databases)

[Django]

#33576: InconsistentMigrationHistory when multiple projects with custom user models
share the same database.
------------------------------+--------------------------------------
Reporter: Artem | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => invalid
* component: Migrations => Core (Other)

Comment:

It's not supported to use the same database for two projects with
different user models because they will share the same tables for reusable
apps e.g. `django.contrib.admin`, see docs about
[https://docs.djangoproject.com/en/stable/topics/auth/customizing/#substituting-a
-custom-user-model Substituting a custom User model]. You will encounter
many other conflicts with such set. Please see
TicketClosingReasons/UseSupportChannels for ways to get help with Django
usage.

--
Ticket URL: <https://code.djangoproject.com/ticket/33576#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.