summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/install.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/topics/install.txt b/docs/topics/install.txt
index 0ee4113c04..52994ed16a 100644
--- a/docs/topics/install.txt
+++ b/docs/topics/install.txt
@@ -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: