Opened 19 months ago
Last modified 19 months ago
#34422 closed Bug
inspectdb mysql databases — at Version 2
| Reported by: | brun806 | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 4.1 |
| Severity: | Normal | Keywords: | inspectdb, mysql, models |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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)
Change History (2)
comment:1 by , 19 months ago
| Component: | Uncategorized → Core (Management commands) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 by , 19 months ago
| Description: | modified (diff) |
|---|---|
| Resolution: | invalid |
| Status: | closed → new |
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.
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.