#17267: MySQL Storage Engines: MyISAM doesn't support Foreign Keys
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.2
Component: Documentation | Keywords: database, mysql,
Severity: Normal | 'storage engine', myisam, 'foreign
Triage Stage: Unreviewed | key'
Easy pickings: 0 | Has patch: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
I was really wondering what this is supposed to mean. How can a Relational
Database not support foreign keys?
So I had to go to to freenode#mysql to ask.
<Vacuity> or to be more precise, myisam doesn't support Foreign Key
_Constraints_
<jay567> so I only have to check myself that the target of the FK is
existant in the target table?
<Vacuity> jay567: it means, although you can define a myisam table with a
CONSTRAINT FOREIGN KEY (col1) REFERENCES othertable (foocol) ON DELETE
CASCADE ... , myisam will ignore this and will not enforce FK constraint
<Vacuity> jay567: yes, you will have to check that yourself
<Vacuity> jay567: if you don't have a very good reason to use myisam, you
should use innodb anyways :)
so
1. This shouldn't be an issue with Django, because it does not rely on the
database for the above check, right?
2. Could you please try to be more clear, so people like me don't need to
wonder (see first two sentences)?
--
Ticket URL: <https://code.djangoproject.com/ticket/17267>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
