mirror of
				https://github.com/django/django.git
				synced 2025-10-31 09:41:08 +00:00 
			
		
		
		
	[1.9.x] Corrected use of 'affect' vs 'effect' in docs.
Backport of 021782d22b from master
			
			
This commit is contained in:
		| @@ -152,7 +152,7 @@ The ``preserve_default`` argument indicates whether the field's default | ||||
| value is permanent and should be baked into the project state (``True``), | ||||
| or if it is temporary and just for this migration (``False``) - usually | ||||
| because the migration is adding a non-nullable field to a table and needs | ||||
| a default value to put into existing rows. It does not effect the behavior | ||||
| a default value to put into existing rows. It does not affect the behavior | ||||
| of setting defaults in the database directly - Django never sets database | ||||
| defaults and always applies them in the Django ORM code. | ||||
|  | ||||
| @@ -180,7 +180,7 @@ The ``preserve_default`` argument indicates whether the field's default | ||||
| value is permanent and should be baked into the project state (``True``), | ||||
| or if it is temporary and just for this migration (``False``) - usually | ||||
| because the migration is altering a nullable field to a non-nullable one and | ||||
| needs a default value to put into existing rows. It does not effect the | ||||
| needs a default value to put into existing rows. It does not affect the | ||||
| behavior of setting defaults in the database directly - Django never sets | ||||
| database defaults and always applies them in the Django ORM code. | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user