http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-1628 Doctrine 2 - ORM <p>It looks like this is in the older documentation (2.0) but not mentioned in the latest.</p> <p>I need to use ON UPDATE CASCADE in a few cases. Seems odd to support onDelete and not onUpdate. Am I missing something?</p> DDC-1628

onUpdate parameter on @JoinColumn not supported

Task Major Closed Invalid Marco Pivetta Chris Richard Tue, 31 Jan 2012 06:21:34 +0000 Wed, 1 May 2013 13:18:11 +0000 Thu, 21 Mar 2013 02:51:46 +0000 2.2 Mapping Drivers 3 5 <p>We removed onUpdate because we couldnt come up with a use-case. CAn you share yours?</p> <p>I assume it's just the mysql driver but all the constraints get created such that you cannot change the primary keys (even if it's not an auto-gen PK). ON UPDATE CASCADE would probably be a better default.</p> <p>I really hope onUpdate annotation attribute will be restored.<br/> I used it in PostgreSQL very often. In some entities in some projects Primary Key ID can be very important its sequence, and if you want to change it, then "ON UPDATE CASCADE" changed it for all the references too. It was must have feature. Now few of my applications are broken with latest doctrine orm.<br/> Please consider restoring it back.<br/> Thank you</p> <p>+1 - onUpdate attribute is very useful for PostgreSQL databases, it controls operations with foreign keys.</p> <p>What do you mean, you couldn't come up with a use-case? If one is migrating data from one table to another and requires that all foreign key references be changed to map the ones in the new table created, before deleting the last table. And there are may more case. Maybe I am missing some thing here, if it's a use-case for the MySQL and PostgreSQL guys, why would you not support it.</p> <p><a href="http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=kenkataiwa" class="user-hover" rel="kenkataiwa">Kenneth Kataiwa</a> updating identifiers is something you don't do, and I sincerely also don't have a use case for this, not in the context of an ORM at least. Also, handling changes in your identifiers in the UnitOfWork is a real problem that adds a lot overhead.</p> <p><cite>+1 - onUpdate attribute is very useful for PostgreSQL databases, it controls operations with foreign keys.</cite></p> <p>I'm taking my words back. It is not a good idea to define onUpdate on foreign keys. Yes, PostgreSQL supports it but it doesn't mean that we should use it in ORM.<br/> Thanks for your time.</p> <p>This issue is invalid, since data migration is not a task for the ORM anyway.</p> <p>I have a third party table which holds users:</p> <p>CREATE TABLE `user`<br/> (<br/> `user_id` INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,<br/> `email` VARCHAR(255) NOT NULL UNIQUE,<br/> ) ENGINE=InnoDB CHARSET="utf8";</p> <p>In my table I want to use natural foreign key, so I reference `email`.</p> <p>CREATE TABLE `transaction` (<br/> `id` INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,<br/> `user_email` VARCHAR(255) NOT NULL,<br/> FOREIGN KEY (`user_email`) REFERENCES `user`(`email`)<br/> );</p> <p>I would like to RDBMS handle email updates on the foreign records.</p> <p>That is a real-life use case of the onDelete, which you decided to remove.<br/> Please, get it back if possible.</p>