#36774: catch DatabaseError instead of OperationalError in makemigrations
check_consistent_history()
-------------------------------------+-------------------------------------
Reporter: Piotr Kubiak | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 6.0
Severity: Normal | Resolution: wontfix
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 Jacob Walls):
* easy: 1 => 0
* resolution: => wontfix
* status: new => closed
Comment:
Thanks for the ticket. I'm concerned the wide catch would hide legitimate
programming errors from other sources (e.g. introspection syntax). This
appears to be a niche use case; you could work around it at the project
level by overriding the migrate command.
--
Ticket URL: <https://code.djangoproject.com/ticket/36774#comment:1>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019ae9d55aba-3d66e18d-0075-4323-8ba5-550034fcfb09-000000%40eu-central-1.amazonses.com.
