On Tue, Jan 5, 2010 at 4:12 PM, Marc Aymerich <[email protected]> wrote: > > > On Tue, Jan 5, 2010 at 8:38 AM, harijay <[email protected]> wrote: >> >> Hi I just started using the subversion build of django and mysql- >> python with python 2.6.3 >> Both django (svn 12103) and _mysql (MySQLdb rev 635) work fine and can >> be imported from the command line python without any error messages. >> I created a new django testproject and then modified my settings.py to >> use the mysql backend ( see DATABASE section below). >> >> But when I start python manage.py runserver 8080 , I get an error >> which I am reproducing here indicating that the backend was not >> started. >> >> Any ideas on what I need to change to have my django launch with the >> mysql backend. >> Thanks >> harijay >> >> The error I get is >> >> ^Chariharan-jayarams-macbook-pro-17:testdjnew hari$ python manage.py >> runserver 8080 >> Validating models... >> Unhandled exception in thread started by <function inner_run at >> 0x7a3670> >> Traceback (most recent call last): >> File "/Users/hari/djtrunk/django/core/management/commands/ >> runserver.py", line 48, in inner_run >> self.validate(display_num_errors=True) >> File "/Users/hari/djtrunk/django/core/management/base.py", line 249, >> in validate >> num_errors = get_validation_errors(s, app) >> File "/Users/hari/djtrunk/django/core/management/validation.py", >> line 22, in get_validation_errors >> from django.db import models, connection >> File "/Users/hari/djtrunk/django/db/__init__.py", line 74, in >> <module> >> connection = connections[DEFAULT_DB_ALIAS] >> File "/Users/hari/djtrunk/django/db/utils.py", line 75, in >> __getitem__ >> backend = load_backend(db['ENGINE']) >> File "/Users/hari/djtrunk/django/db/utils.py", line 37, in >> load_backend >> raise ImproperlyConfigured(error_msg) >> django.core.exceptions.ImproperlyConfigured: >> 'django.db.backends.mysql' isn't an available database backend. >> Try using django.db.backends.XXX, where XXX is one of: >> 'dummy', 'mysql', 'oracle', 'postgresql', 'postgresql_psycopg2', >> 'sqlite3' >> Error was: cannot import name conversions >> >> My settings.py has nothing special after my new settings.py creation >> other than the following database section: >> >> DATABASES = { >> 'default': { >> 'ENGINE': 'django.db.backends.mysql', # Add >> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'. >> 'NAME': 'mytestdb', # Or path to database >> file if using sqlite3. >> 'USER': 'root', # Not used with sqlite3. >> 'PASSWORD': 'mypass', # Not used with >> sqlite3. >> 'HOST': '', # Set to empty string for >> localhost. Not used with sqlite3. >> 'PORT': '', # Set to empty string for >> default. Not used with sqlite3. >> } >> } >> >> > > in 'ENGINE': just put 'mysql'
This is bad advice. Django trunk has changed the preferred way to refer to database engines to a fully qualified path. The old short name approach will still work, but is deprecated. 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 [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-users?hl=en.
