diff options
| author | Tim Graham <timograham@gmail.com> | 2012-10-15 19:54:37 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-10-15 19:56:40 -0400 |
| commit | 81020708eae0a38b56cad86a043a78ffac9ba32a (patch) | |
| tree | 444d2b0b7aecb82ac6e2b237e1a34434f0d41237 | |
| parent | cc0478606a1d3dd804bc005a78e616550d3d0d41 (diff) | |
[1.4.X] Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback.
Backport of 9190d89829 from master
| -rw-r--r-- | docs/topics/install.txt | 10 |
1 files 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: |