p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Edited docs/settings.txt changes from [6316] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6345 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-09-15 22:39:51 +00:00
parent b448593432
commit 1de4bf0b66
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/settings.txt
View File

@ -257,10 +257,11 @@ The database backend to use. The build-in database backends are
``'postgresql_psycopg2'``, ``'postgresql'``, ``'mysql'``, ``'mysql_old'``, ``'postgresql_psycopg2'``, ``'postgresql'``, ``'mysql'``, ``'mysql_old'``,
``'sqlite3'``, ``'oracle'``, or ``'ado_mssql'``. ``'sqlite3'``, ``'oracle'``, or ``'ado_mssql'``.
You can also use a database backend that doesn't ship with Django by In the Django development version, you can use a database backend that doesn't
setting ``DATABASE_ENGINE`` to a fully-qualified path (i.e. ship with Django by setting ``DATABASE_ENGINE`` to a fully-qualified path (i.e.
``mypackage.backends.whatever``). Writing a whole new database backend from ``mypackage.backends.whatever``). Writing a whole new database backend from
scratch is left as an exercise to the reader. scratch is left as an exercise to the reader; see the other backends for
examples.
DATABASE_HOST DATABASE_HOST
------------- -------------