Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fixed #10936 - Noted that using SQLite for development is a good idea

  • Loading branch information...
commit 470deb5cbb765e2e731c5b0b184247c7f87482aa 1 parent 6b56aee
@timgraham timgraham authored
Showing with 6 additions and 1 deletion.
  1. +6 −1 docs/topics/install.txt
View
7 docs/topics/install.txt
@@ -80,7 +80,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:

2 comments on commit 470deb5

@kmtracey
Collaborator

I don't agree with this note. For any application you care about at all you DO need database parity between development and production. There are just way too many places where sqlite fails to catch things that are going to be caught as errors in production. I'm very strongly against Django docs recommending using sqlite for development.

@timgraham
Owner

Thanks Karen, I've added an amended patch to the ticket.

Please sign in to comment.
Something went wrong with that request. Please try again.