ansaurus

Question

Why does django complain that I have not set my ENGINE yet?

Answer 1

+1 A:

I set mine the old way and the new way, so that it's not django-version-specific:

DATABASE_ENGINE   = 'django.db.backends.sqlite3'
DATABASE_NAME     = '/path/to/db/foo.sqlite3'
DATABASE_USER     = ''
DATABASE_PASSWORD = ''
DATABASE_HOST     = ''
DATABASE_PORT     = ''

DATABASES = {
  'default': {
    'ENGINE':   DATABASE_ENGINE,
    'NAME':     DATABASE_NAME,
    'USER':     DATABASE_USER,
    'PASSWORD': DATABASE_PASSWORD,
    'HOST':     DATABASE_HOST,
    'PORT':     DATABASE_PORT,
  }
}

But yeah, I'd double check that your installation is the version you think.

UPDATE:

You may be trying to import something from settings in an admin module, and importing the admin module in settings. Sometimes circular-imports result in the above.

In particular, using reverse("url-name") within settings can cause this, because it ends up forcing it to look at the "site" table at some deep-dark level...

UPDATE2:

Sorry, to explain the above:

A circular import is when a module A imports from module B, and at some level, module B also needs stuff from module A. At some point during that second level of depth, it generally fails in some inscrutable way.
Reverse() is the function to turn a url's name (the name="foo" in urls.py) back into the url itself. This makes calls that are not always possible in settings or admin modules.

UPDATE3:

Looking at the ticket djangobb.org/ticket/81 you pointed to, to break some of the terms down, the csrf token is a template tag used to add Cross Site Request Forgery protection:

http://docs.djangoproject.com/en/dev/ref/contrib/csrf/

It generally looks like this, to grep from a project of mine:

# grep -ri csrf .
  ./registration/login.html:  <form method="post" action="{% url django.contrib.auth.views.login %}">{% csrf_token %}

The bit about the trunk of djapian, though I don't know what djapian is myself, generally means a direct install of the (typically svn) trunk -- or "most up to date, checked in version, which is newer than any release, and possibly tested, official version". Typically, this involves doing something like an svn checkout http://wherever.com/someproject/trunk/ ./someproject and then going to that directory to install.

eruciform 2010-07-14 18:25:36

+1: We've been following eachother around all morning :). This is a good suggestion, and I need to go back and update a few apps that we're created using 1.2, but could also be used w/1.1.

sdolan 2010-07-14 18:30:25

:-) thanks. yeah this one killed me for a while when i moved from 1.1 to 1.2. also an inverse-porting from python 2.6 to 2.4 messed me up badly, as a few libraries depend on the "foo if bar else baz" syntax. i ended up having to install python from scratch on a virtual host just to get 2.6. :-P

eruciform 2010-07-14 18:33:50

I have tried both configuration methods -- djangobb did initially come with the former style in settings.py (I'm assuming this is the previous 1.1 method for database configuration), but again it fails.

Brian D 2010-07-14 18:33:53

updated. might be a circular import or use of reverse() in settings or admin modules.

eruciform 2010-07-14 18:37:37

Sorry, but I'm pretty new to web development and django... what does that mean :P

Brian D 2010-07-14 18:48:55

I don't know where to look .. the settings file looks ok (I didn't see any reverse()... checking admin files, just found them :]). I have django-cms up and running, but this is specific to djangobb

Brian D 2010-07-14 18:54:48

Nah. Nothing noteworthy. I have a feeling it's a result of me running django 1.2 and djangobb requiring 1.1.

Brian D 2010-07-14 18:57:31

sorry about that, updated with some answers. but you may be right, it may come down to djangobb not being ported to django1.2 yet. but if you use the above and go back to 1.1, then your re-port back to django1.2 later will be less painful.

eruciform 2010-07-14 19:05:14

Thanks for the clarification. While I've got your attention, could you explain what they are referring to with the term forms in this porting ticket (with your best guess, I will assume no one in particular uses djangobb): http://djangobb.org/ticket/81.

Brian D 2010-07-14 19:11:29

sure. updated answer for you. :-)

eruciform 2010-07-14 19:32:41

awesome, thanks for your help once again! :)

Brian D 2010-07-14 22:31:28

ansaurus

tags:

views:

answers:

Why does django complain that I have not set my ENGINE yet?

related questions