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-668 Doctrine 2 - ORM <p>Didnt find anything in the docs on this. Is D2 capable of doing an UPSERT <span class="error">&#91;1&#93;</span> in case I am trying to persist an object that may or may not have been saved previously. Different RDBMS support different syntax for this case. Like MySQL has INSERT .. ON DUPLICATE KEY UPDATE (or even INSERT IGNORE) while the SQL standard defines a MERGE syntax which seems to be gaining support. Of course you can always fallback to a SELECT FOR UPDATE (or if you want to be hacky an INSERT which catches duplicate key violations .. but probably not a good idea since many RDBMS rollback on a failure inside a transaction).</p> <p><span class="error">&#91;1&#93;</span> <a href="http://en.wikipedia.org/wiki/Upsert" class="external-link">http://en.wikipedia.org/wiki/Upsert</a></p> <p>See also <a href="http://opensource.atlassian.com/projects/hibernate/browse/HHH-3011" class="external-link">http://opensource.atlassian.com/projects/hibernate/browse/HHH-3011</a> asking for MERGE support</p> <p>Ideally there would be a way to define on a model or model instance level if merge logic should be applied.</p> DDC-668

add upsert support

New Feature Major Open Unresolved All Benjamin Eberlei Lukas Kahwe Sun, 4 Jul 2010 17:20:19 +0000 Tue, 20 Dec 2011 22:22:01 +0000 2.x ORM 4 3 <p>Doctrine_Record defines a replace() method. </p> <p>In the MySQL Doctrine implementation, however, it is not the same as INSERT .. ON DUPLICATE KEY UPDATE. The replace() method implemented in Doctrine_Connection_Mysql uses the REPLACE INTO syntax, which is a DELETE and then INSERT when the key exists. This is fine, except for tables that use auto-increment fields. The delete-then-insert operation yields a new auto-incremented value, whereas INSERT .. ON DUPLICTATE KEY UPDATE would not.</p> <p>MySQL (and SQLite) REPLACE is a no go. It causes way too much disc I/O and worse yet totally screws up the on disk data structures because of the deleting.</p> <p>Scheduled for 2.2</p> <p>Evaluating this makes me sad, except MySQL support for this is rather non-existant, and the oracle merge is aiming at batch operations.</p> <p>Should this be done with</p> <p>1. Select first, then insert<br/> 2. Catch and evaluate exception then update</p> <p>I am leaning towards 1.</p> <p>Updating fix version</p>