#29882: UDFs are not dumped to the clone MySQL test db -------------------------------------+------------------------------------- Reporter: thomazzo | Owner: thomazzo Type: Uncategorized | Status: closed Component: Database layer | Version: 2.1 (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 Dan Davis):
* status: assigned => closed * resolution: => invalid Comment: thomazzo, I've reviewed the general and MySQL specific OPTIONS and settings for the test database, as listed: * here - https://docs.djangoproject.com/en/2.1/ref/settings/#databases * and Here - https://docs.djangoproject.com/en/2.1/ref/databases/#mysql- notes There is no option I'm aware of that would clone the entire database - think of how much time that would take. Also, the whole point of Django's migration support is to allow a developer such as yourself to manage DDL statements needed to define tables, views, functions, stored procedures, and such. Django is an opinionated framework, and it makes table definitions and relationships easy, but if you need custom SQL, it provides mechanisms for including that sort of DDL. So, I think this is not actually a bug. It would be nice if Django's RunSQL migration operation supported filenames, or there was some other migration operation that handled files. However, that is a different feature and someone may already have filed it. -- Ticket URL: <https://code.djangoproject.com/ticket/29882#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/066.57c91f1d7c4b50b7524e53b5d84f976d%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.