mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-02-08 16:35:17 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #35156 -- Removed outdated note about not supporting foreign keys by SQLite.

Browse Source
This commit is contained in:
Ben Cail 2024-01-31 10:27:33 -05:00 committed by Mariusz Felisiak
parent 38eaf2f21a
commit b3dc80682e
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/db/multi-db.txt
View File

@ -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 stored on a separate database, it's not possible to easily evaluate
the validity of a primary key. 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 enforced at the database integrity level -- database level key
constraints prevent the creation of relations that can't be validated. constraints prevent the creation of relations that can't be validated.
However, if you're using SQLite or MySQL with MyISAM tables, there is However, if you're using MySQL with MyISAM tables, there is no enforced
no enforced referential integrity; as a result, you may be able to referential integrity; as a result, you may be able to 'fake' cross database
'fake' cross database foreign keys. However, this configuration is not foreign keys. However, this configuration is not officially supported by
officially supported by Django. Django.
.. _contrib_app_multiple_databases: .. _contrib_app_multiple_databases: