From 81020708eae0a38b56cad86a043a78ffac9ba32a Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 15 Oct 2012 19:54:37 -0400 Subject: [PATCH] [1.4.X] Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback. Backport of 9190d89829 from master --- docs/topics/install.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/topics/install.txt b/docs/topics/install.txt index 1c847c92dc..351fb7126b 100644 --- a/docs/topics/install.txt +++ b/docs/topics/install.txt @@ -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 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: