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

Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback.

This commit is contained in:
Tim Graham 2012-10-15 19:54:37 -04:00
parent 07abb7a6b7
commit 9190d89829
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/install.txt
View File

@ -82,10 +82,12 @@ sure a database server is running. Django supports many different database
servers and is officially supported with PostgreSQL_, MySQL_, Oracle_ and
SQLite_.
It is common practice to use SQLite in a desktop development environment.
Unless you need database feature parity between your desktop development
environment and your deployment environment, using SQLite for development is
generally the simplest option as it doesn't require running a separate server.
If you are developing a simple project or something you don't plan to deploy
in a production environment, SQLite is generally the simplest option as it
doesn't require running a separate server. However, SQLite has many differences
from other databases, so if you are working on something substantial, it's
recommended to develop with the same database as you plan on using in
production.
In addition to the officially supported databases, there are backends provided
by 3rd parties that allow you to use other databases with Django: