#34422: inspectdb mysql databases
-------------------------------------+-------------------------------------
     Reporter:  brun806              |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Core (Management     |                  Version:  4.1
  commands)                          |
     Severity:  Normal               |               Resolution:
     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 brun806):

 * status:  closed => new
 * resolution:  invalid =>


Old description:

> 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.
> could anybody please explain what is happening and how do i fix it?

New description:

 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)

--

Comment:

 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.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34422#comment:2>
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/01070186f48263b9-17e4194d-ede8-496c-9cfb-73998a56e27d-000000%40eu-central-1.amazonses.com.

Reply via email to