| 66 | | For development, most people find SQLite to be fastest and simplest to run with bBut make sure the database and its directory are writeable by the owner of the web server process!). For production, PostgreSQL is probably the most thoroughly-tested of the databases Django supports, but it's best to choose based on the needs of your applications; for example, applications which do very little writing of data to the DB will enjoy the speed of SQLite, but applications which involve many complex queries or which require robust concurrent-write features like transaction isolation will probably want to look at Postgres (and, of course, MySQL is often handy simply because many shared hosting providers have it set up by default). |
| | 66 | For development, most people find SQLite to be fastest and simplest to run with -- just make sure the database file and its directory are writeable by the owner of the web server process. For production, PostgreSQL is probably the most thoroughly-tested of the databases Django supports, but it's best to choose based on the needs of your applications; for example, applications which do very little writing of data to the DB will enjoy the speed of SQLite, but applications which involve many complex queries or which require robust concurrent-write features like transaction isolation will probably want to look at Postgres (and, of course, MySQL is often handy simply because many shared hosting providers have it set up by default). |