#29494: Flush command doesn’t work on custom db_table including schema
-------------------------------------+-------------------------------------
Reporter: Bertrand Bordage | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: duplicate
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 Bertrand Bordage):
* type: Uncategorized => Bug
* version: 2.0 => master
* component: Uncategorized => Database layer (models, ORM)
Comment:
It’s not really true that Django doesn’t support schemas. Some work has
been done to make the `"schema"."table"` trick functional, it was not
possible previously.
And currently, using that trick works flawlessly on PostgreSQL, except
that flushing is silently not done, which can lead to critical data
issues.
Django should explicitly raise an exception when a table name contains a
schema name or a dot instead of the current misleading behaviour.
For the record, I never use these schema tricks, I just chose to support
them in django-cachalot because they seem like valid advanced uses.
Also, #1208 does not suggest a workaround to this issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/29494#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.2724bfdd5d352292ca5d048750d77ec9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
