I mean, at least that's how I reacted upon reading..
"
For MyISAM tables, you can work around the lack of ON DELETE by adding
the appropriate DELETE statement to an application when you delete
records from a table that has a foreign key. In practice this is as
quick (in some cases quicker) and much more portable than using foreign
keys.
"
and
"
A properly written application will make sure internally that it is not
violating referential integrity constraints before proceding with a
query. Thus, additional checks on the database level will only slow down
performance for such an application.
It is not uncommon for a DBA to make such a complex topology of
relations that it becomes very difficult, and in some cases impossible,
to back up or restore individual tables.
"
and I've got the feeling that the only advantage is that I could delete
all related rows in tables that have the foreign key in one query
instead of three or more(take the foreignkey values, delete the row,
delete the rows in the related tables one by one..) That is an
interestesting point because each time I have to code that in an
application, it's error prone and it's not exciting.
Cheers,
Cordialement,
Damien COLA
http://www.VarMalin.com
-----Original Message-----
# [EMAIL PROTECTED] / 2003-04-02 17:37:26 +0200:
> And from this page:
> http://www.mysql.com/doc/en/ANSI_diff_Foreign_Keys.html
> I understand it is rather recommended NOT to use foreign keys, at
> least until mysql integrates it more fully.
which part of that page makes you say that?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
