From 1b49b792e9f0e6a5ae22f49f75586847e7e183bf Mon Sep 17 00:00:00 2001
From: Andrea Rabbaglietti <rabbagliettiandrea@gmail.com>
Date: Wed, 10 Oct 2018 20:56:50 +0200
Subject: [PATCH] Emphasized that ForeignKey.on_delete doesn't create a SQL
 constraint.

---
 docs/ref/models/fields.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index c7e7eb928c..bb2f7fff59 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1271,6 +1271,9 @@ relation works.
             null=True,
         )
 
+    ``on_delete`` doesn't create a SQL constraint in the database. Support for
+    database-level cascade options :ticket:`may be implemented later <21961>`.
+
 The possible values for :attr:`~ForeignKey.on_delete` are found in
 :mod:`django.db.models`: