Removed get_or_create() method, deprecated since 0.8
This commit is contained in:
		| @@ -263,21 +263,11 @@ no document matches the query, and | ||||
| if more than one document matched the query.  These exceptions are merged into | ||||
| your document definitions eg: `MyDoc.DoesNotExist` | ||||
|  | ||||
| A variation of this method exists, | ||||
| :meth:`~mongoengine.queryset.QuerySet.get_or_create`, that will create a new | ||||
| document with the query arguments if no documents match the query. An | ||||
| additional keyword argument, :attr:`defaults` may be provided, which will be | ||||
| used as default values for the new document, in the case that it should need | ||||
| to be created:: | ||||
|  | ||||
|     >>> a, created = User.objects.get_or_create(name='User A', defaults={'age': 30}) | ||||
|     >>> b, created = User.objects.get_or_create(name='User A', defaults={'age': 40}) | ||||
|     >>> a.name == b.name and a.age == b.age | ||||
|     True | ||||
|  | ||||
| .. warning:: | ||||
|     :meth:`~mongoengine.queryset.QuerySet.get_or_create` method is deprecated | ||||
|     since :mod:`mongoengine` 0.8. | ||||
| A variation of this method, get_or_create() existed, but it was unsafe. It | ||||
| could not be made safe, because there are no transactions in mongoDB. Other | ||||
| approaches should be investigated, to ensure you don't accidentally duplicate | ||||
| data when using something similar to this method. Therefore it was deprecated | ||||
| in 0.8 and removed in 0.10. | ||||
|  | ||||
| Default Document queries | ||||
| ======================== | ||||
|   | ||||
		Reference in New Issue
	
	Block a user