#14204: Take advantage of SQLite support for FK constraints
-------------------------------------+-------------------------------------
Reporter: ramiro | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: sqlite, foreign key | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Since it's called an O''R''M, I'm theoretically in favour of focusing on
''relational'' software. Realistically, the main problem is MyISAM. It was
MySQL's default until 5.5. As long as we can't drop the code that works
around databases not enforcing constraints, there's less to gain by
requiring FKs on SQLite.
I'm +1 on enabling FK checks by default in Django and +0 on requiring it
unconditionnally.
--
Ticket URL: <https://code.djangoproject.com/ticket/14204#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.bd8d7332a18e0e9625f60ff9b304f89f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
