#16143: Default settings.py file should fully qualify database name setting
----------------------------------------------+----------------------------
 Reporter:  anonymous                         |          Owner:  nobody
     Type:  Bug                               |         Status:  new
Milestone:                                    |      Component:  Core
  Version:  1.3                               |  (Other)
 Keywords:  settings, database name, sqlite3  |       Severity:  Normal
Has patch:  0                                 |   Triage Stage:  Unreviewed
                                              |  Easy pickings:  1
----------------------------------------------+----------------------------
 While struggling through trying to get a WSGI implementation of
 Django+Pinax up and running, I finally went back to the basics and just
 tried to get an "out of the box" Pinax basic project working.

 It worked fine using the development web server, but failed with the WSGI
 setup.

 I finally narrowed it down to the fact that Apache couldn't find the
 sqlite3 database.  And that was because the name wasn't fully qualified.

 My solution was to change the default definition of the database name in
 settings.py to
         "NAME": os.path.join(PROJECT_ROOT,"dev.db"),

 it was:
         "NAME": "dev.db",


 Not a major bug here, but I believe that the "out of the box" solution
 should work in multiple environments without jumping through a lot of
 hoops.  It just would have made my troubleshooting tonight a lot easier.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16143>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to