Fixed more broken links. refs #19516

   Returns the type of geometry for this feature, as an :class:`OGRGeomType`

   object.  This will be the same for all features in a given layer, and

   is equivalent to the :attr:`Layer.geom_type` property of the

   :class:`Layer`` object the feature came from.

   :class:`Layer` object the feature came from.

   .. attribute:: num_fields

    The name of an orderable field in the model, typically a :class:`DateField`,

    :class:`DateTimeField`, or :class:`IntegerField`. This specifies the default

    field to use in your model :class:`Manager`'s :class:`~QuerySet.latest`

    method.

    field to use in your model :class:`Manager`'s

    :meth:`~django.db.models.query.QuerySet.latest` method.

    Example::

        get_latest_by = "order_date"

    See the docs for :meth:`~django.db.models.query.QuerySet.latest` for more.

    See the :meth:`~django.db.models.query.QuerySet.latest` docs for more.

``managed``

-----------

does not call any ``save()`` methods on your models, nor does it emit the

:attr:`~django.db.models.signals.pre_save` or

:attr:`~django.db.models.signals.post_save` signals (which are a consequence of

calling :meth:`Model.save() <~django.db.models.Model.save()>`). If you want to

calling :meth:`Model.save() <django.db.models.Model.save>`). If you want to

update a bunch of records for a model that has a custom

:meth:`~django.db.models.Model.save()` method, loop over them and call

:meth:`~django.db.models.Model.save()`, like this::

* ``'django.core.cache.backends.memcached.PyLibMCCache'``

You can use a cache backend that doesn't ship with Django by setting

:setting:`BACKEND <CACHE-BACKEND>` to a fully-qualified path of a cache

:setting:`BACKEND <CACHES-BACKEND>` to a fully-qualified path of a cache

backend class (i.e. ``mypackage.backends.whatever.WhateverCache``).

Writing a whole new cache backend from scratch is left as an exercise

to the reader; see the other backends for examples.

Default: :class:`django.views.debug.SafeExceptionReporterFilter`

Default exception reporter filter class to be used if none has been assigned to

the :class:`HttpRequest` instance yet.

the :class:`~django.http.HttpRequest` instance yet.

See :ref:`Filtering error reports<filtering-error-reports>`.

.. setting:: DEFAULT_FILE_STORAGE

See :ref:`initial-data-via-fixtures` and :ref:`topics-testing-fixtures`.

.. setting:: FORCE_SCRIPT_NAME

FORCE_SCRIPT_NAME

------------------

Default: ``()`` (Empty tuple)

A tuple of profanities, as strings, that will be forbidden in comments when

:setting:`COMMENTS_ALLOW_PROFANITIES` is ``False``.

``COMMENTS_ALLOW_PROFANITIES`` is ``False``.

.. setting:: RESTRUCTUREDTEXT_FILTER_SETTINGS

It's now possible to run SQL aggregate queries (i.e. ``COUNT()``, ``MAX()``,

``MIN()``, etc.) from within Django's ORM. You can choose to either return the

results of the aggregate directly, or else annotate the objects in a

:class:`QuerySet` with the results of the aggregate query.

:class:`~django.db.models.query.QuerySet` with the results of the aggregate

query.

This feature is available as new :meth:`QuerySet.aggregate()`` and

:meth:`QuerySet.annotate()`` methods, and is covered in detail in :doc:`the ORM

aggregation documentation </topics/db/aggregation>`

This feature is available as new

:meth:`~django.db.models.query.QuerySet.aggregate` and

:meth:`~django.db.models.query.QuerySet.annotate` methods, and is covered in

detail in :doc:`the ORM aggregation documentation </topics/db/aggregation>`.

Query expressions

~~~~~~~~~~~~~~~~~