That doesn't work for me ( very very strange), that why I am very confused on what is going on with the database itself.
On Sun, Jan 23, 2011 at 8:55 PM, Steven Elliott Jr <steve...@me.com> wrote: > I remember that the one time I tried sqlite it complained until I put a .db > suffix on the name of my database. If you do not specify the full path and > just specify a name, then it will just create the database file in your > project's root directory. > > So, under name just put: > > 'NAME' : 'database.db', > > And see if that works. > > -Steve > Sent from my iPhone > > > On Jan 23, 2011, at 9:48 PM, Graham Dumpleton <graham.dumple...@gmail.com> > wrote: > > > > On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote: >> >> username@debian:~/wikicamps$ python manage.py runserver >> Validating models.... >> 0 errors found >> >> Django version 1.2.4, using settings 'wikicamp.settings' >> Development server is running at <http://127.0.0.1:8000/> >> http://127.0.0.1:8000/ >> Quit the server with CONTROL-C. >> >> It runs fine, but yet I faced problem with the database ENGINE. >> > > Where are you seeing that error because it isn't in what you quote above? > > If it is in the browser, paste the Python exception details and traceback > from the browser. Not everything, just the exception message and traceback > will do. > > In other words, we need to see the actual context in which the real error > message is displayed and the exact wording of the error message and the > location. > > Graham > > >> On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton >> <graham.d...@gmail.com>wrote: >> >>> Provide the full error including any Python traceback so we can see >>> where the error is occurring. If running manage.py runserver, easiest thing >>> to do is to provide the whole output from running the command. >>> >>> Graham >>> >>> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote: >>> >>>> Still doesn't work. But thank you for trying to help me. It keep giving >>>> me the same ENGINE configuration that it is not set. >>>> >>>> On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton >>>> <graha...@gmail.com>wrote: >>>> >>>>> >>>>> >>>>> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote: >>>>>> >>>>>> Sorry about that... here is what I have in the settings.py ( similiar >>>>>> to what you showed, but mine is abit different in the NAME section): >>>>>> >>>>>> DATABASES = { >>>>>> 'default': { >>>>>> 'ENGINE': 'django.db.backends.sqlite3', # Add >>>>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'. >>>>>> 'NAME': 'home/username/directory/database' # >>>>>> Or path to database file if using sqlite3. >>>>>> >>>>> >>>>> You deleted the comma after the string and missing leading slash on >>>>> path. Try: >>>>> >>>>> 'NAME': '/home/username/directory/database', >>>>> # Or path to database file if using sqlite3. >>>>> >>>>> Not sure how you didn't just get a syntax error. >>>>> >>>>> Graham >>>>> >>>>> >>>>>> '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. >>>>>> } >>>>>> } >>>>>> >>>>>> Inside the settings.py file, in the template_dirs section, there's a >>>>>> line says os.path.join(os.path.dirname(_file_), 'templates') >>>>>> >>>>>> If I comment that, then there's a error saying it doesn't recognize >>>>>> _file_. I commented that line, then it says that the setting ENGINE has >>>>>> not >>>>>> been set. >>>>>> >>>>>> >>>>>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton >>>>>> <grah...@gmail.com>wrote: >>>>>> >>>>>>> Rather than have us guess what is in your settings file, post that >>>>>>> whole section. For example: >>>>>>> >>>>>>> DATABASES = { >>>>>>> 'default': { >>>>>>> 'ENGINE': 'django.db.backends.sqlite3', # Add >>>>>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'. >>>>>>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.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. >>>>>>> } >>>>>>> } >>>>>>> >>>>>>> This will allow everyone to see if you have mucked up some other part >>>>>>> of the settings. >>>>>>> >>>>>>> Graham >>>>>>> >>>>>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote: >>>>>>> >>>>>>>> I've used the tutorials and it doesn't work. I've done exactly >>>>>>>> what the tutorial says, and it keeps saying that the ENGINE has not >>>>>>>> been set >>>>>>>> in the setting. I am also using Django 1.2 or higher version. >>>>>>>> >>>>>>>> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey <kmt...@gmail.com>wrote: >>>>>>>> >>>>>>>>> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey < >>>>>>>>> kha...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> it still doesn't work. I typed it like you've suggested and it >>>>>>>>>> keeps saying that the database ENGINE has not been set. >>>>>>>>>> >>>>>>>>>> >>>>>>>>> If you are using ENGINE by itself, you need to be using Django 1.2 >>>>>>>>> or higher and ENGINE is a key in the dictionary of settings for the >>>>>>>>> default >>>>>>>>> database, not a single ENGINE line in settings.py. See: >>>>>>>>> >>>>>>>>> <http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases> >>>>>>>>> http://docs.djangoproject.com/ >>>>>>>>> en/dev/ref/settings/?from=olddocs#databases >>>>>>>>> >>>>>>>>> for details. >>>>>>>>> >>>>>>>>> If you are using a Django version prior to 1.2, the setting you >>>>>>>>> should be using is DATABASE_ENGINE (see >>>>>>>>> <http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine> >>>>>>>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), >>>>>>>>> not just ENGINE. >>>>>>>>> >>>>>>>>> Karen >>>>>>>>> -- >>>>>>>>> <http://tracey.org/kmt/>http://tracey.org/kmt/ >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Django users" group. >>>>>>>>> To post to this group, send email to dja...@googlegroups.com. >>>>>>>>> To unsubscribe from this group, send email to >>>>>>>>> djan...@googlegroups.com. >>>>>>>>> >>>>>>>>> For more options, visit this group at >>>>>>>>> <http://groups.google.com/group/django-users?hl=en> >>>>>>>>> http://groups.google.com/group/django-users?hl=en. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Django users" group. >>>>>>> To post to this group, send email to dja...@googlegroups.com. >>>>>>> To unsubscribe from this group, send email to >>>>>>> djang...@googlegroups.com. >>>>>>> For more options, visit this group at >>>>>>> <http://groups.google.com/group/django-users?hl=en> >>>>>>> http://groups.google.com/group/django-users?hl=en. >>>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django users" group. >>>>> To post to this group, send email to djan...@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>>>> django-...@googlegroups.com. >>>>> For more options, visit this group at >>>>> <http://groups.google.com/group/django-users?hl=en> >>>>> http://groups.google.com/group/django-users?hl=en. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Django users" group. >>> To post to this group, send email to django...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> django-users...@googlegroups.com. >>> For more options, visit this group at >>> <http://groups.google.com/group/django-users?hl=en> >>> http://groups.google.com/group/django-users?hl=en. >>> >> >> -- > 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+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- > 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+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.