From 97a78121b376e3d0818a25b5f0b2e5b5323a4c15 Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Thu, 9 Nov 2023 01:58:06 -0500 Subject: [PATCH] [5.0.x] Fixed typos in docs/ref/models/fields.txt. Backport of 427f0ed98d7ecf4381cebd4f7773f761e2446851 from main --- docs/ref/models/fields.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 7ad9f77741..f90283defc 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1290,8 +1290,8 @@ materialized view. There are many database-specific restrictions on generated fields that Django doesn't validate and the database may raise an error e.g. PostgreSQL - requires functions and operators referenced in a generated columns to be - marked as ``IMMUTABLE`` . + requires functions and operators referenced in a generated column to be + marked as ``IMMUTABLE``. You should always check that ``expression`` is supported on your database. Check out `MariaDB`_, `MySQL`_, `Oracle`_, `PostgreSQL`_, or `SQLite`_