#4429: 500 pages don't work unless you have configured Django database settings
------------------------------+---------------------------------------------
Reporter: Simon Willison | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
There was another ticket opened about the dummy backend recently with
similar issues. I think this is the right way to handle it: by specifying
''dummy'' as the backend, you are saying you don't want the database to
interfere. So having operations default to "always succeeded" feel like
the right thing. ''Dummy'' isn't a very good choice for checking that you
don't use the database at all, so having accesses fail dramatically feels
wong.
--
Ticket URL: <http://code.djangoproject.com/ticket/4429#comment:3>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
