Just let EOF do the Cascade delete based on your relationship options
in EOModeler. In your MySQL InnoDB tables you only need to define your
tables, your PKs and possibly add any UNIQUE INDEX constraints where
your logic dictates ..... nothing more needed by EOF. No need to
define FKs, cascade deletes etc in the db when using MySQL.
On Feb 24, 2009, at 8:27 AM, Pascal Robert wrote:
Hi list,
Can somebody confirm that the MySQL plugin don't care about DELETE
CASCADE rules on a FK in MySQL (4.1)? I switched a small db to
InnoDB and added FK with the DELETE CASCADE option, but EOF still
fetch the parent objects (SELECT * FROM parent), all childs (SELECT
* FROM child) and will issue a DELETE statement for each child...
which is not efficient at all.
-------------------------------------------------------
Pascal Robert
http://www.macti.ca
http://www.aircourriel.com
http://www.linkedin.com/in/macti
Skype: MacTICanada
AIM/iChat : MacTICanada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
