#29882: UDFs are not dumped to the clone MySQL test db
-------------------------------------+-------------------------------------
Reporter: thomazzo | Owner: Dan Davis
Type: Bug | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Dan Davis):
* status: new => assigned
* owner: thomazzo => Dan Davis
Comment:
@adamchainz, I can add a 1-liner there and endeavor to add tests. Is
https://github.com/django/django/blob/55b0b766fbeb2f71e68331a2e14205702f681012/tests/backends/mysql/test_creation.py#L13
the right place to put that test, or it should it tested with a separate
repository because Django's tests are unit tests?
I ask because `django.test.TestCase` is so good it makes most of my tests
really Service Level tests or Database Integration Tests, not really unit
tests. Django itself may have a different philosophy about what the tests
should be and how fast they should run...
--
Ticket URL: <https://code.djangoproject.com/ticket/29882#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f354082e495c840e43f1be117e00995b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
