#22037: Allow testing and dumping legacy database without enabling syncdb ----------------------------------------------+-------------------- Reporter: ellisd23@… | Owner: nobody Type: New feature | Status: new Component: Database layer (models, ORM) | Version: 1.6 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Easy pickings: 0 | UI/UX: 0 ----------------------------------------------+-------------------- I've run into an issue with multiple databases that seems like it could be a common enough use case to warrant taking a look at. I have a legacy database that I am using a database router for. I have reading enabled, but I would prefer not to allow syncdb since writing and changing structures are handled by the legacy application.
Still, for basic read operations such as dumpdata, ``allow_syncdb`` is checked, as well as when creating test databases. My Django app depends on the working legacy database, thus a test database needs to be created as well. For now I'm overriding this will a custom setting that is modified at run time to indicate whether ``syncdb`` should be allowed, but this is obviously not a good long-term solution. -- Ticket URL: <https://code.djangoproject.com/ticket/22037> 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/061.fc740c0ddc01bc477dae64f8d87a9761%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.