Ticket #8849: new-in-django-dev.diff

File new-in-django-dev.diff, 4.7 KB (added by ramiro, 7 years ago)
  • docs/ref/generic-views.txt

    diff -r 1f1e091f0f7b docs/ref/generic-views.txt
    a b The ``django.views.generic.create_update 
    868868The ``django.views.generic.create_update`` module contains a set of functions
    869869for creating, editing and deleting objects.
    870870
    871 **Changed in Django development version:**
     871.. versionchanged:: 1.0
    872872
    873873``django.views.generic.create_update.create_object`` and
    874874``django.views.generic.create_update.update_object`` now use the new :ref:`forms
  • docs/ref/models/fields.txt

    diff -r 1f1e091f0f7b docs/ref/models/fields.txt
    a b can change the maximum length using the  
    571571
    572572.. class:: FloatField([**options])
    573573
    574 **Changed in Django development version**
     574.. versionchanged:: 1.0
    575575
    576576A floating-point number represented in Python by a ``float`` instance.
    577577
  • docs/ref/models/instances.txt

    diff -r 1f1e091f0f7b docs/ref/models/instances.txt
    a b To save an object back to the database,  
    3535
    3636Of course, there are some subtleties; see the sections below.
    3737
    38 **New in Django development version:** The signature of the ``save()`` method
    39 has changed from earlier versions (``force_insert`` and ``force_update`` have
    40 been added). If you are overriding these methods, be sure to use the correct
    41 signature.
     38.. versionadded:: 1.0
     39
     40The signature of the ``save()`` method has changed from earlier versions
     41(``force_insert`` and ``force_update`` have been added). If you are overriding
     42these methods, be sure to use the correct signature.
    4243
    4344Auto-incrementing primary keys
    4445------------------------------
  • docs/ref/models/querysets.txt

    diff -r 1f1e091f0f7b docs/ref/models/querysets.txt
    a b ordering may well be exactly what you wa 
    176176ordering may well be exactly what you want to do. Use ordering on multi-valued
    177177fields with care and make sure the results are what you expect.
    178178
    179 **New in Django development version:** If you don't want any ordering to be
    180 applied to a query, not even the default ordering, call ``order_by()`` with no
    181 parameters.
     179.. versionadded:: 1.0
    182180
    183 **New in Django development version:** The syntax for ordering across related
    184 models has changed. See the `Django 0.96 documentation`_ for the old behaviour.
     181If you don't want any ordering to be applied to a query, not even the default
     182ordering, call ``order_by()`` with no parameters.
     183
     184.. versionadded:: 1.0
     185
     186The syntax for ordering across related models has changed. See the `Django 0.96
     187documentation`_ for the old behaviour.
    185188
    186189.. _Django 0.96 documentation: http://www.djangoproject.com/documentation/0.96/model-api/#floatfield
    187190
    A couple of subtleties that are worth me 
    291294      ordering can affect the results. See the note in the `distinct()`_
    292295      section, above, for details.
    293296
    294 **New in Django development version:** Previously, it was not possible to pass
    295 ``blog_id`` to ``values()`` in the above example, only ``blog``.
     297.. versionadded:: 1.0
     298
     299Previously, it was not possible to pass ``blog_id`` to ``values()`` in the above
     300example, only ``blog``.
    296301
    297302A ``ValuesQuerySet`` is useful when you know you're only going to need values
    298303from a small number of the available fields and you won't need the
    individualism. 
    314319``values_list(*fields)``
    315320~~~~~~~~~~~~~~~~~~~~~~~~
    316321
    317 **New in Django development version**
     322.. versionadded:: 1.0
    318323
    319324This is similar to ``values()`` except that instead of returning a list of
    320325dictionaries, it returns a list of tuples. Each tuple contains the value from
    follow:: 
    459464    c = p.hometown       # Requires a database call.
    460465
    461466.. versionadded:: 1.0
    462    The ``depth`` argument is new in the Django development version.
     467
     468The ``depth`` argument is new in Django version 1.0.
    463469
    464470``extra(select=None, where=None, params=None, tables=None, order_by=None, select_params=None)``
    465471~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • docs/topics/db/models.txt

    diff -r 1f1e091f0f7b docs/topics/db/models.txt
    a b for details. 
    528528
    529529.. _One-to-one relationship model example: http://www.djangoproject.com/documentation/models/one_to_one/
    530530
    531 **New in Django development version**
     531.. versionadded:: 1.0
    532532
    533533:class:`~django.db.models.OneToOneField` fields also accept one optional argument
    534534described in the :ref:`model field reference <ref-onetoone>`.
Back to Top