Re: Tutorial database problem

OK, problem solved. The location I thought was working for django 1.4
was different than was actually the case. I'm reinstalling to a new
location and hope it will work correctly this time.

The advice on adding the divide by 0 line helped since it didn't
execute.

Thanks,

Mark


On May 28, 4:57 am, Gelonida N <gelon...@gmail.com> wrote:
> On 05/27/2012 05:38 AM, phantom21 wrote:
>
>
>
>
>
>
>
>
>
> > I've tried to set up the database as sqlite3.  I keep getting an error
> > on the ENGINE line, but can't figure out why as it looks correct.
>
> > Here is the database section:
>
> > DATABASES = {
> >      'default': {
> >          'ENGINE': 'django.db.backends.sqlite3',
> >          'NAME': '/usr/bin/sqlite3/mark.db',  # Or path to database
> > file if using sqlite3
> >          'USER': '',                      # Not used with sqlite3.
> >          'PASSWORD': '',                  # 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.
> >      }
> > }
>
> > And here is the error I receive:
>
> > Traceback (most recent call last):
> >    File "manage.py", line 10, in<module>
> >      execute_from_command_line(sys.argv)
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > __init__.py", line 443, in execute_from_command_line
> >      utility.execute()
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > __init__.py", line 382, in execute
> >      self.fetch_command(subcommand).run_from_argv(self.argv)
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > base.py", line 196, in run_from_argv
> >      self.execute(*args, **options.__dict__)
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > base.py", line 232, in execute
> >      output = self.handle(*args, **options)
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > base.py", line 371, in handle
> >      return self.handle_noargs(**options)
> >    File "/usr/local/lib/python2.7/dist-packages/django/core/management/
> > commands/syncdb.py", line 57, in handle_noargs
> >      cursor = connection.cursor()
> >    File "/usr/local/lib/python2.7/dist-packages/django/db/backends/
> > dummy/base.py", line 15, in complain
> >      raise ImproperlyConfigured("settings.DATABASES is improperly
> > configured. "
> > django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
> > improperly configured. Please supply the ENGINE value. Check settings
> > documentation for more details.
>
> Well your DATABASES settings look fine (except of the path of the NAME
> entry as others have already pointed out.
> To be very sure there are no permission problems
>
> Do you get the error already when running the command
>
> python manage.py syncdb
>
> For testing you could add following line as LAST line in settings.py
>
> print 'DATABASES = %r' % DATABASES
>
> and paste the results to your next answer.
> Printing with %r has also the advantage of revealing any hidden characters.
>
> Are you sure, that django uses the setting.py file, that you modified???
>
> If you're not sure, than add following line as the FIRST line in settings.py
> a = 1 / 0
>
> If Django fails now with a division by zero you're sure it's using the
> file you think it's using and you can remove this line again.

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.