From 8139a7990a682f282096167bcea35004cacf5559 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 11 Oct 2012 19:54:52 -0400 Subject: [PATCH] [1.4.X] Fixed #10936 - Noted that using SQLite for development is a good idea Backport of 470deb5cbb from master --- docs/topics/install.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/topics/install.txt b/docs/topics/install.txt index 7ac0710174..1c847c92dc 100644 --- a/docs/topics/install.txt +++ b/docs/topics/install.txt @@ -82,7 +82,12 @@ Get your database running If you plan to use Django's database API functionality, you'll need to make sure a database server is running. Django supports many different database servers and is officially supported with PostgreSQL_, MySQL_, Oracle_ and -SQLite_ (although SQLite doesn't require a separate server to be running). +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. In addition to the officially supported databases, there are backends provided by 3rd parties that allow you to use other databases with Django: