Opened 11 years ago

Closed 11 years ago

#5255 closed (fixed)

DATABASE_ENGINE error when starting new site

Reported by: Hendrik van der Linde <vlipper@…> Owned by: Jacob
Component: Uncategorized Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


When I start a new site, and start the server, I get errors. I have not done any configuration, but I don't need much, because I don't want to use a database (as a workaround I am now using sqlite3). Latest svn revision (6001).

Below the command I ran and the errors.

python runserver
Validating models...
Unhandled exception in thread started by <function inner_run at 0x10e1f70>
Traceback (most recent call last):

File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/management/commands/", line 40, in inner_run


File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/management/", line 59, in validate

num_errors = get_validation_errors(s, app)

File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/management/", line 21, in get_validation_errors

from django.db import models, connection

File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/models/", line 6, in ?

from django.db.models.query import Q

File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/models/", line 568, in ?

if connection.features.uses_custom_queryset:

File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/backends/dummy/", line 26, in getattr


File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/db/backends/dummy/", line 13, in complain

raise ImproperlyConfigured, "You haven't set the DATABASE_ENGINE setting yet."

django.core.exceptions.ImproperlyConfigured: You haven't set the DATABASE_ENGINE setting yet.

Change History (1)

comment:1 Changed 11 years ago by Adrian Holovaty

Resolution: fixed
Status: newclosed

(In [6002]) Fixed #5255 -- It's now possible again to use Django without a database. This had temporarily gotten buggy after the refactoring last week

Note: See TracTickets for help on using tickets.
Back to Top