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:55:46 -0400 |
| commit | 9190d89829c4e0b9b0f36e1c717ea451a1a13efd (patch) | |
| tree | ab4635512e4d67b9284381d517bdbf592b4c56ec /docs/topics | |
| parent | 07abb7a6b7af2c45be553acf08d85cd2d72057ad (diff) | |
Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback.
Diffstat (limited to 'docs/topics')
| -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 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: |