#18053: empty DATABASES blows up in 1.4 -------------------------------------+------------------------------------- Reporter: anonymous | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.4 (models, ORM) | Resolution: Severity: Normal | Triage Stage: Accepted Keywords: | Needs documentation: 0 Has patch: 0 | Patch needs improvement: 0 Needs tests: 0 | UI/UX: 0 Easy pickings: 0 | -------------------------------------+-------------------------------------
Comment (by ptone): Ideally it would be nice to see if this can be fixed by examining the places where db/__init__ is being invoked by import and factor those parts that actually need the db, vs those that don't. IOW see what it would take to allow a truly blank databases setting at the global conf level. The simpler fix would be to special check for a blank databases in db/__init__ and set the dummy backend as in global settings. -- Ticket URL: <https://code.djangoproject.com/ticket/18053#comment:2> 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 post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.