#34422: inspectdb mysql databases
-------------------------------------+-------------------------------------
Reporter: brun806 | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: 4.1
commands) |
Severity: Normal | Resolution: invalid
Keywords: inspectdb, mysql, | Triage Stage:
models | 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
Comment:
Replying to [ticket:34422 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34422#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186f4b020f1-f4c1af90-3fe4-41a2-988f-a7824b1cefa9-000000%40eu-central-1.amazonses.com.
