mirror of
https://github.com/django/django.git
synced 2025-07-24 13:44:32 +00:00
Fixed #34851 -- Dropped support for PostgreSQL 12 and PostGIS 2.5.
This commit is contained in:
parent
0b506bfe1a
commit
2c6ebb65c9
12 changed files with 32 additions and 47 deletions
|
@ -12,7 +12,7 @@ Program Description Required
|
|||
`PROJ`_ Cartographic Projections library Yes (PostgreSQL and SQLite only) 9.x, 8.x, 7.x, 6.x, 5.x
|
||||
:doc:`GDAL <../gdal>` Geospatial Data Abstraction Library Yes 3.7, 3.6, 3.5, 3.4, 3.3, 3.2, 3.1, 3.0, 2.4
|
||||
:doc:`GeoIP <../geoip2>` IP-based geolocation library No 2
|
||||
`PostGIS`__ Spatial extensions for PostgreSQL Yes (PostgreSQL only) 3.4, 3.3, 3.2, 3.1, 3.0, 2.5
|
||||
`PostGIS`__ Spatial extensions for PostgreSQL Yes (PostgreSQL only) 3.4, 3.3, 3.2, 3.1, 3.0
|
||||
`SpatiaLite`__ Spatial extensions for SQLite Yes (SQLite only) 5.0, 4.3
|
||||
======================== ==================================== ================================ ===========================================
|
||||
|
||||
|
@ -35,7 +35,6 @@ totally fine with GeoDjango. Your mileage may vary.
|
|||
GDAL 3.5.0 2022-05-13
|
||||
GDAL 3.6.0 2022-11-03
|
||||
GDAL 3.7.0 2023-05-10
|
||||
PostGIS 2.5.0 2018-09-23
|
||||
PostGIS 3.0.0 2019-10-20
|
||||
PostGIS 3.1.0 2020-12-18
|
||||
PostGIS 3.2.0 2021-12-18
|
||||
|
|
|
@ -56,7 +56,7 @@ supported versions, and any notes for each of the supported database backends:
|
|||
================== ============================== ================== =========================================
|
||||
Database Library Requirements Supported Versions Notes
|
||||
================== ============================== ================== =========================================
|
||||
PostgreSQL GEOS, GDAL, PROJ, PostGIS 12+ Requires PostGIS.
|
||||
PostgreSQL GEOS, GDAL, PROJ, PostGIS 13+ Requires PostGIS.
|
||||
MySQL GEOS, GDAL 8.0.11+ :ref:`Limited functionality <mysql-spatial-limitations>`.
|
||||
Oracle GEOS, GDAL 19+ XE not supported.
|
||||
SQLite GEOS, GDAL, PROJ, SpatiaLite 3.27.0+ Requires SpatiaLite 4.3+
|
||||
|
|
|
@ -30,7 +30,7 @@ Post-installation
|
|||
Creating a spatial database
|
||||
---------------------------
|
||||
|
||||
PostGIS 2 includes an extension for PostgreSQL that's used to enable spatial
|
||||
PostGIS includes an extension for PostgreSQL that's used to enable spatial
|
||||
functionality:
|
||||
|
||||
.. code-block:: shell
|
||||
|
@ -50,9 +50,9 @@ process. An alternative is to use a migration operation in your project::
|
|||
class Migration(migrations.Migration):
|
||||
operations = [CreateExtension("postgis"), ...]
|
||||
|
||||
If you plan to use PostGIS raster functionality on PostGIS 3+, you should also
|
||||
activate the ``postgis_raster`` extension. You can install the extension using
|
||||
the :class:`~django.contrib.postgres.operations.CreateExtension` migration
|
||||
If you plan to use PostGIS raster functionality, you should also activate the
|
||||
``postgis_raster`` extension. You can install the extension using the
|
||||
:class:`~django.contrib.postgres.operations.CreateExtension` migration
|
||||
operation, or directly by running ``CREATE EXTENSION postgis_raster;``.
|
||||
|
||||
GeoDjango does not currently leverage any `PostGIS topology functionality`__.
|
||||
|
|
|
@ -114,7 +114,7 @@ below for information on how to set up your database correctly.
|
|||
PostgreSQL notes
|
||||
================
|
||||
|
||||
Django supports PostgreSQL 12 and higher. `psycopg`_ 3.1.8+ or `psycopg2`_
|
||||
Django supports PostgreSQL 13 and higher. `psycopg`_ 3.1.8+ or `psycopg2`_
|
||||
2.8.4+ is required, though the latest `psycopg`_ 3.1.8+ is recommended.
|
||||
|
||||
.. note::
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue