Refs #33872 -- Removed django.contrib.postgres.fields.CIText/CICharField/CIEmailField/CITextField.

Per deprecation timeline.

2 files changed, 9 insertions, 68 deletions

diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt
index e641c989e3..9170ff83a8 100644
--- a/docs/ref/checks.txt
+++ b/docs/ref/checks.txt
@@ -237,13 +237,19 @@ Model fields
   except for support in historical migrations.
 * **fields.W905**: ``django.contrib.postgres.fields.CICharField`` is
   deprecated. Support for it (except in historical migrations) will be removed
-  in Django 5.1.
+  in Django 5.1. *This check appeared in Django 4.2 and 5.0*.
+* **fields.E905**: ``django.contrib.postgres.fields.CICharField`` is removed
+  except for support in historical migrations.
 * **fields.W906**: ``django.contrib.postgres.fields.CIEmailField`` is
   deprecated. Support for it (except in historical migrations) will be removed
-  in Django 5.1.
+  in Django 5.1. *This check appeared in Django 4.2 and 5.0*.
+* **fields.E906**: ``django.contrib.postgres.fields.CIEmailField`` is removed
+  except for support in historical migrations.
 * **fields.W907**: ``django.contrib.postgres.fields.CITextField`` is
   deprecated. Support for it (except in historical migrations) will be removed
-  in Django 5.1.
+  in Django 5.1. *This check appeared in Django 4.2 and 5.0*.
+* **fields.E907**: ``django.contrib.postgres.fields.CITextField`` is removed
+  except for support for historical migrations.
 
 File fields
 ~~~~~~~~~~~
diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt
index 0348bb235f..ec767b50e9 100644
--- a/docs/ref/contrib/postgres/fields.txt
+++ b/docs/ref/contrib/postgres/fields.txt
@@ -277,71 +277,6 @@ transform do not change. For example:
     at the database level and cannot be supported in a logical, consistent
     fashion by Django.
 
-``CIText`` fields
-=================
-
-.. class:: CIText(**options)
-
-    .. deprecated:: 4.2
-
-    A mixin to create case-insensitive text fields backed by the citext_ type.
-    Read about `the performance considerations`_ prior to using it.
-
-    To use ``citext``, use the :class:`.CITextExtension` operation to
-    :ref:`set up the citext extension <create-postgresql-extensions>` in
-    PostgreSQL before the first ``CreateModel`` migration operation.
-
-    If you're using an :class:`~django.contrib.postgres.fields.ArrayField`
-    of ``CIText`` fields, you must add ``'django.contrib.postgres'`` in your
-    :setting:`INSTALLED_APPS`, otherwise field values will appear as strings
-    like ``'{thoughts,django}'``.
-
-    Several fields that use the mixin are provided:
-
-.. class:: CICharField(**options)
-
-    .. deprecated:: 4.2
-
-        ``CICharField`` is deprecated in favor of
-        ``CharField(db_collation="…")`` with a case-insensitive
-        non-deterministic collation.
-
-.. class:: CIEmailField(**options)
-
-    .. deprecated:: 4.2
-
-        ``CIEmailField`` is deprecated in favor of
-        ``EmailField(db_collation="…")`` with a case-insensitive
-        non-deterministic collation.
-
-.. class:: CITextField(**options)
-
-    .. deprecated:: 4.2
-
-        ``CITextField`` is deprecated in favor of
-        ``TextField(db_collation="…")`` with a case-insensitive
-        non-deterministic collation.
-
-    These fields subclass :class:`~django.db.models.CharField`,
-    :class:`~django.db.models.EmailField`, and
-    :class:`~django.db.models.TextField`, respectively.
-
-    ``max_length`` won't be enforced in the database since ``citext`` behaves
-    similar to PostgreSQL's ``text`` type.
-
-    .. _citext: https://www.postgresql.org/docs/current/citext.html
-    .. _the performance considerations: https://www.postgresql.org/docs/current/citext.html#id-1.11.7.19.9
-
-.. admonition:: Case-insensitive collations
-
-    It's preferable to use non-deterministic collations instead of the
-    ``citext`` extension. You can create them using the
-    :class:`~django.contrib.postgres.operations.CreateCollation` migration
-    operation. For more details, see :ref:`manage-postgresql-collations` and
-    the PostgreSQL documentation about `non-deterministic collations`_.
-
-    .. _non-deterministic collations: https://www.postgresql.org/docs/current/collation.html#COLLATION-NONDETERMINISTIC
-
 ``HStoreField``
 ===============