On Monday, April 2, 2012 8:35:28 AM UTC-7, Optimus Paul wrote:
>
> I've been running Django for quite a while without a "database", we
> use MongoDB, and it has worked well for us. We upgraded to 1.4 and
> found that suddenly a default database is required. Is there a reason
> for this? Or is this a bug?
>
> We get the error when importing django.shortcuts.render_to_response,
> which doesn't seem like the kind of place a database connection would
> even be required.
Any chance you have an explicit empty DATABASES={} setting? Try deleting
that setting entirely and see if it works.
As part of the removal of the backwards compatibility shim for the old
DATABASE_* settings, the global settings contains a DATABASES setting that
uses the dummy backend for the default database. This global setting will
silence the import errors, but still raise an error if you try to do
anything that uses the DB.
-Preston
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/bAjgMbeYb-wJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
