#33537: Cloning test databases should reraise errors on MySQL.
-------------------------------------+-------------------------------------
Reporter: Stephen Finucane | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"1823a8011346afc280e0efaf8cb7c086b148f881" 1823a801]:
{{{#!CommitTicketReference repository=""
revision="1823a8011346afc280e0efaf8cb7c086b148f881"
Fixed #33537 -- Made test database cloning on MySQL reraise unexpected
errors.
Thanks Faakhir Zahid and Stephen Finucane for the initial patch.
Thanks Simon Charette for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33537#comment:16>
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/01070195a490e36f-0097857d-4614-4187-94ce-37597f792a16-000000%40eu-central-1.amazonses.com.
