From 6564bfec85616869b933994a2eda3be87f661db2 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Fri, 15 Aug 2008 12:16:10 +0000 Subject: [PATCH] Fixed #6551: clarify the meaning of ``DATABASE_NAME`` for SQLite in docs/tutorial01.txt git-svn-id: http://code.djangoproject.com/svn/django/trunk@8374 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/tutorial01.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/tutorial01.txt b/docs/tutorial01.txt index 9e765b1a9b..6d7b10a053 100644 --- a/docs/tutorial01.txt +++ b/docs/tutorial01.txt @@ -145,8 +145,12 @@ database's connection parameters: * ``DATABASE_ENGINE`` -- Either 'postgresql_psycopg2', 'mysql' or 'sqlite3'. Other backends are `also available`_. - * ``DATABASE_NAME`` -- The name of your database, or the full (absolute) - path to the database file if you're using SQLite. + * ``DATABASE_NAME`` -- The name of your database. If you're using + SQLite, the database will be a file on your computer; in that + case, ``DATABASE_NAME`` should be the full absolute path, + including filename, of that file. If the file doesn't exist, it + will automatically be created when you synchronize the database + for the first time (see below). * ``DATABASE_USER`` -- Your database username (not used for SQLite). * ``DATABASE_PASSWORD`` -- Your database password (not used for SQLite). * ``DATABASE_HOST`` -- The host your database is on. Leave this as an