diff options
| author | Ben Cail <bcail@crossway.org> | 2024-01-31 10:27:33 -0500 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2024-01-31 18:35:30 +0100 |
| commit | d28c61b777d69e8be724da9287d2bc74c784b802 (patch) | |
| tree | 71a86f8e107e69ccd19c3f4d586e1b448ba0906e /docs | |
| parent | 7453d6a80792e3f811fc662b8b25fdcbc5ea7eb3 (diff) | |
[5.0.x] Fixed #35156 -- Removed outdated note about not supporting foreign keys by SQLite.
Backport of b3dc80682e678b20c89fb2a430c0bc77960a29ac from main
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/multi-db.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt index 8da71df250..be7e9953fa 100644 --- a/docs/topics/db/multi-db.txt +++ b/docs/topics/db/multi-db.txt @@ -740,14 +740,14 @@ primary key of the related object is valid. If the primary key is stored on a separate database, it's not possible to easily evaluate the validity of a primary key. -If you're using Postgres, Oracle, or MySQL with InnoDB, this is +If you're using Postgres, SQLite, Oracle, or MySQL with InnoDB, this is enforced at the database integrity level -- database level key constraints prevent the creation of relations that can't be validated. -However, if you're using SQLite or MySQL with MyISAM tables, there is -no enforced referential integrity; as a result, you may be able to -'fake' cross database foreign keys. However, this configuration is not -officially supported by Django. +However, if you're using MySQL with MyISAM tables, there is no enforced +referential integrity; as a result, you may be able to 'fake' cross database +foreign keys. However, this configuration is not officially supported by +Django. .. _contrib_app_multiple_databases: |