mirror of
				https://github.com/django/django.git
				synced 2025-10-31 01:25:32 +00:00 
			
		
		
		
	[1.5.x] Documentation - Noted that OneToOneField doesn't respect unique.
Added OneToOneField to the list of model fields for which the unique argument isn't valid. (OneToOneFields are inherently unique, and if the user supplies a value for unique it is ignored / overwritten.)
This commit is contained in:
		
				
					committed by
					
						 Preston Holmes
						Preston Holmes
					
				
			
			
				
	
			
			
			
						parent
						
							adf70506b9
						
					
				
				
					commit
					bbe2ad3e38
				
			| @@ -269,8 +269,8 @@ you try to save a model with a duplicate value in a :attr:`~Field.unique` | ||||
| field, a :exc:`django.db.IntegrityError` will be raised by the model's | ||||
| :meth:`~django.db.models.Model.save` method. | ||||
|  | ||||
| This option is valid on all field types except :class:`ManyToManyField` and | ||||
| :class:`FileField`. | ||||
| This option is valid on all field types except :class:`ManyToManyField`, | ||||
| :class:`OneToOneField`, and :class:`FileField`. | ||||
|  | ||||
| Note that when ``unique`` is ``True``, you don't need to specify | ||||
| :attr:`~Field.db_index`, because ``unique`` implies the creation of an index. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user