  rollback that would be performed by ``transaction.rollback()``.
  
  .. versionchanged:: 1.6
  
  When the :func:`atomic` decorator is nested, it creates a savepoint to allow
  partial commit or rollback. You're strongly encouraged to use :func:`atomic`
  rather than the functions described below, but they're still part of the
  public API, and there's no plan to deprecate them.
  
  Each of these functions takes a ``using`` argument which should be the name of
  a database for which the behavior applies.  If no ``using`` argument is
  provided then the ``"default"`` database is used.
  
 
</s> remove         Historically, this parameter was only called ``mimetype`` (now
        deprecated), but since this is actually the value included in the HTTP
        ``Content-Type`` header, it can also include the character set
        encoding, which makes it more than just a MIME type specification. If
        ``mimetype`` is specified (not ``None``), that value is used.
        Otherwise, ``content_type`` is used. If neither is given,
        :setting:`DEFAULT_CONTENT_TYPE` is used.
 </s> add             Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used. </s> remove The behavior by which introspected models are created as unmanaged ones is new
in Django 1.6.
 </s> add     The behavior by which introspected models are created as unmanaged ones is new
    in Django 1.6. </s> remove In previous versions of Django, the ``pk`` attribute had to be present
on the serialized data or a ``DeserializationError`` would be raised.
 </s> add     In previous versions of Django, the ``pk`` attribute had to be present
    on the serialized data or a ``DeserializationError`` would be raised. </s> remove This technique is fragile and was deprecated in Django 1.5. If you need the
response to be streamed from the iterator to the client, you should use the
:class:`StreamingHttpResponse` class instead.
 </s> add     This technique is fragile and was deprecated in Django 1.5. If you need the
    response to be streamed from the iterator to the client, you should use the
    :class:`StreamingHttpResponse` class instead. </s> remove         ``success_url`` may contain dictionary string formatting, which
        will be interpolated against the object's field attributes. For
        example, you could use ``success_url="/parent/%(parent_id)s/"`` to
        redirect to a URL composed out of the ``parent_id`` field on a model.
 </s> add             ``success_url`` may contain dictionary string formatting, which
            will be interpolated against the object's field attributes. For
            example, you could use ``success_url="/parent/%(parent_id)s/"`` to
            redirect to a URL composed out of the ``parent_id`` field on a model.
    When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
  rollback that would be performed by ``transaction.rollback()``.
  
  .. versionchanged:: 1.6
  
    When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
    When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
    When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
    When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
  
  Each of these functions takes a ``using`` argument which should be the name of
  a database for which the behavior applies.  If no ``using`` argument is
  provided then the ``"default"`` database is used.
  
keep keep keep keep replace replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/topics/db/transactions.txt