diff options
| author | Tim Graham <timograham@gmail.com> | 2012-10-11 19:54:52 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-10-11 20:02:40 -0400 |
| commit | 8139a7990a682f282096167bcea35004cacf5559 (patch) | |
| tree | 8d3e8688f289755b76394cbc26bb2a536a00c7ef /docs | |
| parent | a1d21c08774c87b8d2995aada5ad20c650ad7570 (diff) | |
[1.4.X] Fixed #10936 - Noted that using SQLite for development is a good idea
Backport of 470deb5cbb from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/install.txt | 7 |
1 files changed, 6 insertions, 1 deletions
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: |