On 04/02/2012 09:35 AM, 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?
Preston has the right solution for this - delete your DATABASES setting entirely. I think it would be best if an empty DATABASES setting had the same effect, especially since that's how it was in 1.3 - if you'd be willing to file a ticket for that, that'd be great. > 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. render_to_response doesn't require a database, but there are other functions in django.shortcuts that do (e.g. get_object_or_404), and the error is triggered on any import of django.db.* Carl
signature.asc
Description: OpenPGP digital signature
