diff options
| author | Tim Graham <timograham@gmail.com> | 2014-12-26 13:56:08 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-01-17 10:16:06 -0500 |
| commit | 4aa089a9a9504c4a833eee8161be013206da5d15 (patch) | |
| tree | ebc7e23d3805c57d9f6a4fc75767b5e5046617a4 /docs/ref/models | |
| parent | a420f83e7d2e446ca01ef7c13d30c2ef3e975e5c (diff) | |
Removed support for custom SQL per deprecation timeline.
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/fields.txt | 3 |
1 files changed, 1 insertions, 2 deletions
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<initial-sql>`). + you manually add an SQL ``ON DELETE`` constraint to the database field. .. attribute:: ForeignKey.swappable |