Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Symfony2 Doctrine merge

I am studying https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/reference/working-with-associations.html but I cannot figure out what cascade merge does. I have seen elsewhere that

$new_object = $em->merge($object); 

basically creates a new managed object based on $object. Is that correct?

like image 348
mentalic Avatar asked Apr 05 '13 12:04

mentalic


People also ask

How doctrine works?

Doctrine uses the Identity Map pattern to track objects. Whenever you fetch an object from the database, Doctrine will keep a reference to this object inside its UnitOfWork. The array holding all the entity references is two-levels deep and has the keys root entity name and id.

What is a repository doctrine?

A repository in a term used by many ORMs (Object Relational Mappers), doctrine is just one of these. It means the place where our data can be accessed from, a repository of data. This is to distinguish it from a database as a repository does not care how its data is stored.

What is doctrine persist?

The Doctrine Persistence project is a set of shared interfaces and functionality that the different Doctrine object mappers share. You can use these interfaces and abstract classes to build your own mapper if you don't want to use the full data mappers provided by Doctrine.


2 Answers

$em->merge() is used to take an Entity which has been taken out of the context of the entity manager and 'reattach it'.

  • If the Entity was never managed, merge is equivalent to persist.
  • If the Entity was detached, or serialized (put in a cache perhaps) then merge more or less looks up the id of the entity in the data store and then starts tracking any changes to the entity from that point on.

Cascading a merge extends this behavior to associated entities of the one you are merging. This means that changes are cascaded to the associations and not just the entity being merged.

like image 166
james_t Avatar answered Sep 22 '22 11:09

james_t


I know this is an old question, but I think it is worth mentioning that $em->merge() is deprecated and will be removed soon. Check here

Merge operation is deprecated and will be removed in Persistence 2.0. Merging should be part of the business domain of an application rather than a generic operation of ObjectManager.

Also please read this doc v3 how they expect entities to be stored

https://www.doctrine-project.org/projects/doctrine-orm/en/latest/cookbook/entities-in-session.html#entities-in-the-session

It is a good idea to avoid storing entities in serialized formats such as $_SESSION: instead, store the entity identifiers or raw data.

like image 34
Kiren S Avatar answered Sep 18 '22 11:09

Kiren S