[Django] #33248: inspectdb command. foreignkey on_delete always get DO_NOTHING
Django
------------------------------------------+------------------------
Reporter: Jiangshan00001 | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
when i use inspectdb command.
the on_delete parameter of the ForeignKey field is always DO_NOTHING.
but my database is not set as DO_NOTHING.
I noticed that the output file has this line:
"Make sure each ForeignKey and OneToOneField has `on_delete` set to the
desired behavior"
I'd like to know,
why no don't get the information from database?
is this a bug, or just no use for some reason?
--
Ticket URL: <https://code.djangoproject.com/ticket/33248>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: Jiangshan00001 | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
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: Uncategorized => Database layer (models, ORM)
Comment:
Replying to [ticket:33248 Jiangshan00001]:
> I'd like to know,
> why no don't get the information from database?
>
> is this a bug, or just no use for some reason?
Django doesn't support database-level cascade options and doesn’t create
an SQL constraint in the database, so there is no way to introspect it,
see #21961.
--
Ticket URL: <https://code.djangoproject.com/ticket/33248#comment:1>