Browse files

Fixed #6551: clarify the meaning of ``DATABASE_NAME`` for SQLite in d…


git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 57aa1fd commit 6564bfec85616869b933994a2eda3be87f661db2 @ubernostrum ubernostrum committed Aug 15, 2008
Showing with 6 additions and 2 deletions.
  1. +6 −2 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

0 comments on commit 6564bfe

Please sign in to comment.