[1.4.X] Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback.

Backport of 9190d89829 from master
This commit is contained in:
Tim Graham 2012-10-15 19:54:37 -04:00
parent cc0478606a
commit 81020708ea
1 changed files with 6 additions and 4 deletions

View File

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