Didnt find anything in the docs on this. Is D2 capable of doing an UPSERT  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).
See also http://opensource.atlassian.com/projects/hibernate/browse/HHH-3011 asking for MERGE support
Ideally there would be a way to define on a model or model instance level if merge logic should be applied.
|Field||Original Value||New Value|
|Assignee||Roman S. Borschel [ romanb ]||Benjamin Eberlei [ beberlei ]|
|Fix Version/s||2.2-DEV [ 10157 ]|
|Fix Version/s||2.x [ 10090 ]|
|Fix Version/s||2.2 [ 10157 ]|
|Workflow||jira [ 11585 ]||jira-feedback [ 13856 ]|
|Workflow||jira-feedback [ 13856 ]||jira-feedback2 [ 15720 ]|
|Workflow||jira-feedback2 [ 15720 ]||jira-feedback3 [ 17977 ]|