inspectdb mysql databases

[brun806]

i think there is some bug in inspectdb command. now when i manually use in terminal
python manage.py inspectdb > models.py
it generates ONLY models where name starts with “Auth” and “Django”.
when i use
python manage.py inspectdb --database=“data” > models.py
it creates models ONLY for that database.
but previously it generated models for both database and models that are part of Django’s built-in authentication and content types framework in a single models.py.
(using Windows 10, MySQL, Python 3.9.1 and Django 4.1.7)

[Tim Graham]

This isn't a support channel. See TicketClosingReasons/UseSupportChannels for ways to get help if you can't debug the issue on your own. Feel free to reopen this issue if you find problem in Django and can explain where the issue lies.

[brun806]

Ticket was closed by Tim Graham, with "This isn't a support channel. See TicketClosingReasons/UseSupportChannels for ways to get help if you can't debug the issue on your own. Feel free to reopen this issue if you find problem in Django and can explain where the issue lies."
I deleted question and leaved only description of the problem.

[Mariusz Felisiak]

Replying to brun806:

i think there is some bug in inspectdb command. now when i manually use in terminal
python manage.py inspectdb > models.py
it generates ONLY models where name starts with “Auth” and “Django”.
when i use
python manage.py inspectdb --database=“data” > models.py
it creates models ONLY for that database.
but previously it generated models for both database and models that are part of Django’s built-in authentication and content types framework in a single models.py.
(using Windows 10, MySQL, Python 3.9.1 and Django 4.1.7)

This is still a support question, and described behavior is expected. inspectdb respects the database parameter and use the default database when not provided.
Please don't reopen this ticket and use support channels if you have further questions/doubts.