mirror of
				https://github.com/django/django.git
				synced 2025-10-31 01:25:32 +00:00 
			
		
		
		
	[1.4.X] Fixed #10936 - Tempered recommendation of SQLite - thanks Karen Tracey for the feedback.
Backport of 9190d89829 from master
			
			
This commit is contained in:
		| @@ -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: | ||||
|   | ||||
		Reference in New Issue
	
	Block a user