After testing with the older revisions, I found that revision 5976 is the one that caused the problem:
Revision: 5976 Author: adrian Date: 5:39:05 AM, Monday, August 20, 2007 Message: Refactored get_query_set_class() to DatabaseOperations.query_set_class(). Also added BaseDatabaseFeatures.uses_custom_queryset. Refs #5106 ---- Modified : /django/trunk/django/db/backends/__init__.py Modified : /django/trunk/django/db/backends/oracle/base.py Modified : /django/trunk/django/db/models/query.py This revision makes the server complain that the DATABASE_ENGINE is not set. Later revisions work if I only add the line: DATABASE_ENGINE = 'postgresql_psycopg2' to the settings.py Cheers, oMat On 25 Ağustos, 13:53, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 8/25/07, omat <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > After a recent svn update, my no-database django application is > > broken. > > Could you help us out here and tell us what constitutes a 'recent SVN > update'? What was the last version that worked? Which version have you > updated to? > > > Something changed, and now the DATABASE_ENGINE setting became required > > and its absence results in an ImproperlyConfigured error, even if the > > application does not use a db backend. Beware. > > Again - more details would be helpful. When are you seeing the > problem? How does it manifest? Can you produce a simple test > application that demonstrates the problem? > > At a guess, the problem will be related to the recent management.py > refactor, but without details, it's difficult to say for certain. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
