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:01:30 -0400 |
| commit | 470deb5cbb765e2e731c5b0b184247c7f87482aa (patch) | |
| tree | 8d866e63bedc9c1dbad7988910898b561c7f894d | |
| parent | 6b56aeec6e21c1cf7eccfd89f0f5c6722a066efc (diff) | |
Fixed #10936 - Noted that using SQLite for development is a good idea
| -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 39b9a93c04..0ee4113c04 100644 --- a/docs/topics/install.txt +++ b/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: |