From 4aa089a9a9504c4a833eee8161be013206da5d15 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 26 Dec 2014 13:56:08 -0500 Subject: Removed support for custom SQL per deprecation timeline. --- docs/ref/models/fields.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'docs/ref/models') diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 8604137afe..39d728bbce 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1295,8 +1295,7 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in Take no action. If your database backend enforces referential integrity, this will cause an :exc:`~django.db.IntegrityError` unless - you manually add an SQL ``ON DELETE`` constraint to the database field - (perhaps using :ref:`initial sql`). + you manually add an SQL ``ON DELETE`` constraint to the database field. .. attribute:: ForeignKey.swappable -- cgit v1.3