Fixed #23152 -- Added support for transactional Spatialite metadata initialization.

from django.contrib.gis.db.backends.spatialite.operations import SpatiaLiteOperations

from django.contrib.gis.db.backends.spatialite.schema import SpatialiteSchemaEditor

from django.utils import six

from django.utils.functional import cached_property

class DatabaseFeatures(BaseSpatialFeatures, SQLiteDatabaseFeatures):

    # SpatiaLite can only count vertices in LineStrings

    supports_num_points_poly = False

    @cached_property

    def supports_initspatialmetadata_with_transactions(self):

        # SpatiaLite 4.1+ support initializing all metadata in one transaction

        # which can result in a significant performance improvement when

        # creating the database.

        return self.connection.ops.spatial_version >= (4, 1, 0)

class DatabaseWrapper(SQLiteDatabaseWrapper):

    SchemaEditorClass = SpatialiteSchemaEditor

        Creates the spatial metadata tables.

        """

        cur = self.connection._cursor()

        cur.execute("SELECT InitSpatialMetaData()")

        arg = "1" if self.connection.features.supports_initspatialmetadata_with_transactions else ""

        cur.execute("SELECT InitSpatialMetaData(%s)" % arg)

  ``AlterIndexTogether`` or ``AlterUniqueTogether`` (:ticket:`23614`).

* Updated the first day of the week in the Ukrainian locale to Monday.

* Added support for transactional spatial metadata initialization on

  SpatiaLite 4.1+ (:ticket:`23152`).