**NOTE : if what I want is not possible, a &quot;not possible&quot; answer will be accepted**

In the [Doctrine 2 documentation about **inheritance mapping**][1], it says there are 2 ways :

 - Single table inheritance (STI)
 - Class table inheritance (CTI)

For both, there is the warning :

&gt; If you use a STI/CTI entity as a many-to-one or one-to-one entity **you should never use one of the classes at the upper levels** of the inheritance hierachy as “targetEntity”, only those that have no subclasses. Otherwise Doctrine CANNOT create proxy instances of this entity and will ALWAYS load the entity eagerly.

So, how can I proceed **to use inheritance with an association to the base (abstract) class** ? (and keep the performance of course)


----------


Example
-------

A user has many `Pet` (abstract class extended by `Dog` or `Cat`).

What I want to do :

    class User {
        /**
         * @var array(Pet) (array of Dog or Cat)
         */
        private $pets;
    }

Because of the warning in Doctrine documentation, I should do that :

    class User {
        /**
         * @var array(Dog)
         */
        private $dogs;
        /**
         * @var array(Cat)
         */
        private $cats;
    }

**This is annoying, because I loose the benefits of inheritance !**

*Note : I didn&#39;t add the Doctrine annotations for the mapping to DB, but you can understand what I mean* 

  [1]: http://www.doctrine-project.org/docs/orm/2.0/en/reference/inheritance-mapping.html

Doctrine 2 Inheritance Mapping with Association

How do I use Doctrine in a service container?

The Code just causes an error message &quot;Fatal error: Call to undefined method ...::get()&quot;.

    &lt;?php
        
    namespace ...\Service;

    use Doctrine\ORM\EntityManager;
    use ...\Entity\Header;

    class dsdsf
    { 
        protected $em;

        public function __construct(EntityManager $em)
        {
            $this-&gt;em = $em;
        }
	
        public function create()
        {
            $id = 10;
            $em = $this-&gt;get(&#39;doctrine&#39;)-&gt;getEntityManager();
            $em-&gt;getRepository(&#39;...&#39;)-&gt;find($id);
        }
    }

services.yml

    service:
        site:
            class: ...\Service\Site

Symfony2 Use Doctrine in Service Container

I&#39;m wondering what&#39;s the best, the cleanest and the most simply way to work with many-to-many relations in Doctrine2. 

Let&#39;s assume that we&#39;ve got an album like [*Master of Puppets* by Metallica](http://www.last.fm/music/Metallica/Master+of+Puppets) with several tracks. But please note the fact that one track might appears in more that one album, like [*Battery* by Metallica](http://www.last.fm/music/Metallica/Master+of+Puppets/Battery) does - three albums are featuring this track.

So what I need is many-to-many relationship between albums and tracks, using third table with some additional columns (like position of the track in specified album). Actually I have to use, as Doctrine&#39;s documentation suggests, a double one-to-many relation to achieve that functionality.

    /** @Entity() */
    class Album {
    	/** @Id @Column(type=&quot;integer&quot;) */
    	protected $id;
    	
    	/** @Column() */
    	protected $title;
    	
    	/** @OneToMany(targetEntity=&quot;AlbumTrackReference&quot;, mappedBy=&quot;album&quot;) */
    	protected $tracklist;
    	
    	public function __construct() {
    		$this-&gt;tracklist = new \Doctrine\Common\Collections\ArrayCollection();
    	}
    	
    	public function getTitle() {
    		return $this-&gt;title;
    	}
    	
    	public function getTracklist() {
    		return $this-&gt;tracklist-&gt;toArray();
    	}
    }
    
    /** @Entity() */
    class Track {
    	/** @Id @Column(type=&quot;integer&quot;) */
    	protected $id;
    	
    	/** @Column() */
    	protected $title;
    	
    	/** @Column(type=&quot;time&quot;) */
    	protected $duration;
    	
    	/** @OneToMany(targetEntity=&quot;AlbumTrackReference&quot;, mappedBy=&quot;track&quot;) */
    	protected $albumsFeaturingThisTrack; // btw: any idea how to name this relation? :)
    	
    	public function getTitle() {
    		return $this-&gt;title;
    	}
    	
    	public function getDuration() {
    		return $this-&gt;duration;
    	}
    }
    
    /** @Entity() */
    class AlbumTrackReference {
    	/** @Id @Column(type=&quot;integer&quot;) */
    	protected $id;
    	
    	/** @ManyToOne(targetEntity=&quot;Album&quot;, inversedBy=&quot;tracklist&quot;) */
    	protected $album;
    	
    	/** @ManyToOne(targetEntity=&quot;Track&quot;, inversedBy=&quot;albumsFeaturingThisTrack&quot;) */
    	protected $track;
    	
    	/** @Column(type=&quot;integer&quot;) */
    	protected $position;
    	
    	/** @Column(type=&quot;boolean&quot;) */
    	protected $isPromoted;
    	
    	public function getPosition() {
    		return $this-&gt;position;
    	}
    	
    	public function isPromoted() {
    		return $this-&gt;isPromoted;
    	}
    	
    	public function getAlbum() {
    		return $this-&gt;album;
    	}
    	
    	public function getTrack() {
    		return $this-&gt;track;
    	}
    }

Sample data:

                 Album
    +----+--------------------------+
    | id | title                    |
    +----+--------------------------+
    |  1 | Master of Puppets        |
    |  2 | The Metallica Collection |
    +----+--------------------------+
    
                   Track
    +----+----------------------+----------+
    | id | title                | duration |
    +----+----------------------+----------+
    |  1 | Battery              | 00:05:13 |
    |  2 | Nothing Else Matters | 00:06:29 |
    |  3 | Damage Inc.          | 00:05:33 |
    +----+----------------------+----------+
    
                  AlbumTrackReference
    +----+----------+----------+----------+------------+
    | id | album_id | track_id | position | isPromoted |
    +----+----------+----------+----------+------------+
    |  1 |        1 |        2 |        2 |          1 |
    |  2 |        1 |        3 |        1 |          0 |
    |  3 |        1 |        1 |        3 |          0 |
    |  4 |        2 |        2 |        1 |          0 |
    +----+----------+----------+----------+------------+

Now I can display a list of albums and tracks associated to them:

    $dql = &#39;
    	SELECT   a, tl, t
    	FROM     Entity\Album a
    	JOIN     a.tracklist tl
    	JOIN     tl.track t
    	ORDER BY tl.position ASC
    &#39;;
    
    $albums = $em-&gt;createQuery($dql)-&gt;getResult();
    
    foreach ($albums as $album) {
    	echo $album-&gt;getTitle() . PHP_EOL;
    	
    	foreach ($album-&gt;getTracklist() as $track) {
    		echo sprintf(&quot;\t#%d - %-20s (%s) %s\n&quot;, 
    			$track-&gt;getPosition(),
    			$track-&gt;getTrack()-&gt;getTitle(),
    			$track-&gt;getTrack()-&gt;getDuration()-&gt;format(&#39;H:i:s&#39;),
    			$track-&gt;isPromoted() ? &#39; - PROMOTED!&#39; : &#39;&#39;
    		);
    	}	
    }

The results are what I&#39;m expecting, ie: a list of albums with their tracks in appropriate order and promoted ones being marked as promoted.

    The Metallica Collection
    	#1 - Nothing Else Matters (00:06:29) 
    Master of Puppets
    	#1 - Damage Inc.          (00:05:33) 
    	#2 - Nothing Else Matters (00:06:29)  - PROMOTED!
    	#3 - Battery              (00:05:13) 

## So what&#39;s wrong?

This code demonstrates what&#39;s wrong:

    foreach ($album-&gt;getTracklist() as $track) {
        echo $track-&gt;getTrack()-&gt;getTitle();
    }

`Album::getTracklist()` returns an array of `AlbumTrackReference` objects instead of `Track` objects. I can&#39;t create proxy methods cause what if both, `Album` and `Track` would have `getTitle()` method? I could do some extra processing within `Album::getTracklist()` method but what&#39;s the most simply way to do that? Am I forced do write something like that?

    public function getTracklist() {
        $tracklist = array();
    
        foreach ($this-&gt;tracklist as $key =&gt; $trackReference) {
            $tracklist[$key] = $trackReference-&gt;getTrack();
     
            $tracklist[$key]-&gt;setPosition($trackReference-&gt;getPosition());
            $tracklist[$key]-&gt;setPromoted($trackReference-&gt;isPromoted());
        }
    
        return $tracklist;
    }
    
    // And some extra getters/setters in Track class

#EDIT

@beberlei suggested to use proxy methods:

    class AlbumTrackReference {
        public function getTitle() {
            return $this-&gt;getTrack()-&gt;getTitle()
        }
    }

That would be a good idea but I&#39;m using that &quot;reference object&quot; from both sides: `$album-&gt;getTracklist()[12]-&gt;getTitle()` and `$track-&gt;getAlbums()[1]-&gt;getTitle()`, so `getTitle()` method should return different data based on the context of invocation.

I would have to do something like:

     getTracklist() {
         foreach ($this-&gt;tracklist as $trackRef) { $trackRef-&gt;setContext($this); }
     }

     // ....
   
     getAlbums() {
         foreach ($this-&gt;tracklist as $trackRef) { $trackRef-&gt;setContext($this); }
     }

     // ...

     AlbumTrackRef::getTitle() {
          return $this-&gt;{$this-&gt;context}-&gt;getTitle();
     }

And that&#39;s not a very clean way.

Doctrine2: Best way to handle many-to-many with extra columns in reference table

Is there an easy way to check for duplicate keys with Doctrine 2 before doing a flush?

Checking for duplicate keys with Doctrine 2

We&#39;re using Doctrine, a PHP ORM. I am creating a query like this:

    $q = Doctrine_Query::create()-&gt;select(&#39;id&#39;)-&gt;from(&#39;MyTable&#39;);

and then in the function I&#39;m adding in various where clauses and things as appropriate, like this

    $q-&gt;where(&#39;normalisedname = ? OR name = ?&#39;, array($string, $originalString));

Later on, before ``execute()``-ing that query object, I want to print out the raw SQL in order to examine it, and do this:

    $q-&gt;getSQLQuery();

However that only prints out the prepared statement, not the full query. I want to see what it is sending to the MySQL, but instead it is printing out a prepared statement, including ``?``&#39;s. Is there some way to see the &#39;full&#39; query?

Doctrine - How to print out the real sql, not just the prepared statement?

I need to order data by two columns (when the rows have different values for column number 1, order by it; otherwise, order by column number 2)

I&#39;m using a `QueryBuilder` to create the query.

If I call the `orderBy` method a second time, it replaces any previously specified orderings.

I can pass two columns as the first parameter:

    -&gt;orderBy(&#39;r.firstColumn, r.secondColumn&#39;, &#39;DESC&#39;);

But I cannot pass two ordering directions for the second parameter, so when I execute this query the first column is ordered in an ascending direction and the second one, descending. I would like to use descending for both of them.

Is there a way to do this using `QueryBuilder`? Do I need to use DQL?

Order by multiple columns with Doctrine

I&#39;m starting a new project with [symfony][1] which is readily integrated with [Doctrine][2] and [Propel][3], but I of course need to make a choice.... I was wondering if more experienced people out there have general pros and/or cons for going with either of these two?

Thanks a lot.

**EDIT:**
Thanks for the all the responses, useful stuff. There&#39;s no truly correct answer to this question so I&#39;ll just mark as approved the one that got the most popular up-votes.


  [1]: http://www.symfony-project.org/
  [2]: http://www.doctrine-project.org/
  [3]: http://www.propelorm.org/

PHP ORMs: Doctrine vs. Propel

An `User` has one `Package` associated with it. Many users can refer to the same package. `User` cannot exists without a `Package` defined. `User` should own the relation. Relation is bidirectional, so a `Package` has zero or more users in it. 

These requirements lead to `ManyToOne` relation for `User` and `OneToMany` relation of `Package` in Doctrine 2. However `package_id` in `user` table (that is foreign-key) allows `null` values. I&#39;ve tried setting `nullable=false` but command:

     php app/console doctrine:generate:entities DL --path=&quot;src&quot; --no-backup

Says that there is no attribute `nullable` for the relation `ManyToOne`. **What i&#39;m missing?**

    class User
    {
    
        /**
         * @ORM\Id
         * @ORM\Column(type=&quot;integer&quot;)
         * @ORM\GeneratedValue(strategy=&quot;AUTO&quot;)
         */
        private $id;
    
        /**
         * @ORM\ManyToOne(targetEntity=&quot;Package&quot;, inversedBy=&quot;users&quot;)
         */
        private $package;
    
    }

    class Package
    {
    
        /**
         * @ORM\Id
         * @ORM\Column(type=&quot;integer&quot;)
         * @ORM\GeneratedValue(strategy=&quot;AUTO&quot;)
         */
        private $id;
    
        /**
         * @ORM\OneToMany(targetEntity=&quot;User&quot;, mappedBy=&quot;package&quot;)
         */
        private $users;
    
    }

Doctrine 2 can&#39;t use nullable=false in manyToOne relation?

I want to execute raw SQL using Doctrine 2

I need to truncate the database tables and initialize tables with default test data.




Execute raw SQL using Doctrine 2

My entity uses this annotation for it&#39;s ID:

&lt;!-- language: lang-php --&gt;

    /**
     * @orm:Id
     * @orm:Column(type=&quot;integer&quot;)
     * @orm:GeneratedValue(strategy=&quot;AUTO&quot;)
     */
    protected $id;

From a clean database, I&#39;m importing in existing records from an older database and trying to keep the same IDs.  Then, when adding new records, I want MySQL to auto-increment the ID column as usual.

Unfortunately, it appears Doctrine2 completely ignores the specified ID.

- - -

**New Solution**

Per recommendations below, the following is the preferred solution:

&lt;!-- language: lang-php --&gt;

    $this-&gt;em-&gt;persist($entity);
    
    $metadata = $this-&gt;em-&gt;getClassMetaData(get_class($entity));
    $metadata-&gt;setIdGeneratorType(\Doctrine\ORM\Mapping\ClassMetadata::GENERATOR_TYPE_NONE);
    $metadata-&gt;setIdGenerator(new \Doctrine\ORM\Id\AssignedGenerator());


**Old Solution**

Because Doctrine pivots off of the ClassMetaData for determining the generator strategy, it has to be modified after managing the entity in the EntityManager:

&lt;!-- language: lang-php --&gt;

    $this-&gt;em-&gt;persist($entity);
    
    $metadata = $this-&gt;em-&gt;getClassMetaData(get_class($entity));
    $metadata-&gt;setIdGeneratorType(\Doctrine\ORM\Mapping\ClassMetadata::GENERATOR_TYPE_NONE);

    $this-&gt;em-&gt;flush();

I just tested this on MySQL and it worked as expected, meaning Entities with a custom ID were stored with that ID, while those without an ID specified used the `lastGeneratedId() + 1`.

Explicitly set Id with Doctrine when using &quot;AUTO&quot; strategy

I tried to gather some information about the following way to delete automatically child entity when a parent entity is deleted. Seems that the most common way is to use one those three annotation: `cascade={&quot;remove&quot;}` OR `orphanRemoval=true` OR `ondelete=&quot;CASCADE&quot;`. 

 I am a bit confused about the third one: `ondelete=&quot;CASCADE&quot;`, as the explanation in doctrine official documentation about this one are very scarce) and I would love if someone could **confirm me the following information** I gathered and understand from my research on the net and experience...   

What does it do?

`cascade={&quot;remove&quot;}`
==&gt; the entity on the inverse side is deleted when the owning side entity is. Even if you are in a `ManyToMany` with other owning side entity.   
- should be used on collection (so in `OneToMany` or `ManyToMany` relationship)  
- implementation in the ORM

`orphanRemoval=true`
==&gt; the entity on the inverse side is deleted when the owning side entity is AND it is not connected to any other owning side entity anymore. (ref.  [doctrine official_doc](http://doctrine-orm.readthedocs.org/en/latest/reference/xml-mapping.html?highlight=orphanremoval#defining-many-to-one-associations)
- implementation in the ORM   
- can be used with `OneToOne`, `OneToMany` or `ManyToMany`

`onDelete=&quot;CASCADE&quot;` 
==&gt; this will add On Delete Cascade to the foreign key column in the database  
- This strategy is a bit tricky to get right but can be very powerful and fast. (ref.  [doctrine official_doc](http://doctrine-orm.readthedocs.org/en/latest/reference/working-with-objects.html?highlight=tricky#removing-entities) ... but haven&#39;t read more explanations)   
- ORM has to do less work (compared to the two previous ways of doing it) and therefore should have better performance.

**other information**   
- all those 3 ways of doing are implemented on bidirectional relationship entities (**_right???_**)    
- using `cascade={&quot;remove&quot;}` completely by-passes any foreign key onDelete=CASCADE. (ref. [doctrine_official_doc](http://doctrine-orm.readthedocs.org/en/latest/reference/working-with-objects.html?highlight=tricky#removing-entities))


EXAMPLE ON HOW TO USE IT IN CODE
--
- `orphanRemoval` and `cascade={&quot;remove&quot;}` are defined in the inversed entity class.  
- `ondelete=&quot;CASCADE&quot;` is defined in the owner entity
- you can also just write `@ORM\JoinColumn(onDelete=&quot;CASCADE&quot;)` and let doctrine handle the column names

**cascade={&quot;remove&quot;}**

    /**
    * @OneToMany(targetEntity=&quot;Phonenumber&quot;, mappedBy=&quot;contact&quot;, cascade={&quot;remove&quot;})
    */
    protected $Phonenumbers

 
**orphanRemoval=true**

    /**
    * @OneToMany(targetEntity=&quot;Phonenumber&quot;, mappedBy=&quot;contact&quot;, orphanRemoval=true)
    */
    protected $Phonenumbers

**onDelete=&quot;CASCADE&quot;**

    /** 
    * @ManyToOne(targetEntity=&quot;Contact&quot;, inversedBy=&quot;phonenumbers&quot;)
    * @JoinColumn(name=&quot;contact_id&quot;, referencedColumnName=&quot;contact_id&quot;, onDelete=&quot;CASCADE&quot;)
    */ 
    protected $contact; 



cascade={&quot;remove&quot;} VS orphanRemoval=true VS ondelete=&quot;CASCADE

I&#39;ve read about hydration in doctrine&#39;s documentation but I still can&#39;t understand what it is.

Could someone please explain?

What is Doctrine hydration?

I&#39;m developing game app and using Symfony 2.0. I have many AJAX requests to the backend. And more responses is converting entity to JSON. For example: 

    class DefaultController extends Controller
    {           
        public function launchAction()
        {   
            $user = $this-&gt;getDoctrine()
                         -&gt;getRepository(&#39;UserBundle:User&#39;)                
                         -&gt;find($id);
     
            // encode user to json format
            $userDataAsJson = $this-&gt;encodeUserDataToJson($user);
            return array(
                &#39;userDataAsJson&#39; =&gt; $userDataAsJson
            );            
        }
       
        private function encodeUserDataToJson(User $user)
        {
            $userData = array(
                &#39;id&#39; =&gt; $user-&gt;getId(),
                &#39;profile&#39; =&gt; array(
                    &#39;nickname&#39; =&gt; $user-&gt;getProfile()-&gt;getNickname()
                )
            );
            
            $jsonEncoder = new JsonEncoder();        
            return $jsonEncoder-&gt;encode($userData, $format = &#39;json&#39;);
        }
    }

And all my controllers do the same thing: get an entity and encode some of its fields to JSON. I know that I can use normalizers and encode all entitities. But what if an entity has cycled links to other entity? Or the entities graph is very big? Do you have any suggestions? 

I think about some encoding schema for entities... or using `NormalizableInterface` to avoid cycling..,

How to encode Doctrine entities to JSON in Symfony 2.0 AJAX application?

Let&#39;s suppose I retrieve an entity `$e` and modify its state with setters:

    $e-&gt;setFoo(&#39;a&#39;);
    $e-&gt;setBar(&#39;b&#39;);

Is there any possibility to retrieve an array of fields that have been changed?

In case of my example I&#39;d like to retrieve `foo =&gt; a, bar =&gt; b` as a result

PS: yes, I know I can modify all the accessors and implement this feature manually, but I&#39;m looking for some handy way of doing this

Is there a built-in way to get all of the changed/updated fields in a Doctrine 2 entity

since 2 weeks, we are having this problem while trying to flush new elements:
&gt;CRITICAL: Doctrine\ORM\ORMInvalidArgumentException:
&gt;
A new entity was found through the relationship &#39;Comment#capture&#39; that was not configured to cascade persist operations for entity

But the `capture` is already in the database, and we are getting it by a `findOneBy`, so if we cascade persist it, or persist it, we get a
&gt;Table constraint violation: duplicate entry.

The comments are created in a loop with differents captures, with a new, and all required field are set.

With all of the entities persisted and / or got by a `findOne` (and all valid), the flush still fails.


I&#39;m on this issue since a while, so please help me

Doctrine - A new entity was found through the relationship

I&#39;ve got the following query but it doesn&#39;t seem to work.

    $q = $this-&gt;em-&gt;createQueryBuilder()
        -&gt;update(&#39;models\User&#39;, &#39;u&#39;)
        -&gt;set(&#39;u.username&#39;, $username)
        -&gt;set(&#39;u.email&#39;, $email)
        -&gt;where(&#39;u.id = ?1&#39;)
        -&gt;setParameter(1, $editId)
        -&gt;getQuery();
    $p = $q-&gt;execute();

This returns the following error message:

&gt; Fatal error: Uncaught exception
&gt; &#39;Doctrine\ORM\Query\QueryException&#39;
&gt; with message &#39;[Semantical Error] line
&gt; 0, col 38 near &#39;testusername WHERE&#39;:
&gt; Error: &#39;testusername&#39; is not defined.&#39;
&gt; in ...

I would be glad of any help

Doctrine 2: Update query with query builder

I&#39;m using Symfony 4.3.8 and I can&#39;t find any information about thoses deprecations :

&gt; User Deprecated: Creating Doctrine\ORM\Mapping\UnderscoreNamingStrategy without making it number aware is deprecated and will be removed in Doctrine ORM 3.0.
&gt; 
&gt; Creating Doctrine\ORM\Mapping\UnderscoreNamingStrategy without making it number aware is deprecated and will be removed in Doctrine ORM 3.0.

I searched in stacktrace and found this :

    class UnderscoreNamingStrategy implements NamingStrategy
    {
    private const DEFAULT_PATTERN      = &#39;/(?&lt;=[a-z])([A-Z])/&#39;;
    private const NUMBER_AWARE_PATTERN = &#39;/(?&lt;=[a-z0-9])([A-Z])/&#39;;

    /**
     * Underscore naming strategy construct.
     *
     * @param int $case CASE_LOWER | CASE_UPPER
     */
    public function __construct($case = CASE_LOWER, bool $numberAware = false)
    {
        if (! $numberAware) {
            @trigger_error(
                &#39;Creating &#39; . self::class . &#39; without making it number aware is deprecated and will be removed in Doctrine ORM 3.0.&#39;,
                E_USER_DEPRECATED
            );
        }

        $this-&gt;case    = $case;
        $this-&gt;pattern = $numberAware ? self::NUMBER_AWARE_PATTERN : self::DEFAULT_PATTERN;
    }

In this class, the constructor is always called without params, so $numberAware is always false.

This class is called in file which has been auto generated by the Symfony Dependency Injection, so I can&#39;t &quot;edit&quot; it ...

I thought maybe it was in doctrine.yaml :

    doctrine:
    orm:
        auto_generate_proxy_classes: true
        naming_strategy: doctrine.orm.naming_strategy.underscore
        auto_mapping: true
        mappings:
            App:
                is_bundle: false
                type: annotation
                dir: &#39;%kernel.project_dir%/src/Entity&#39;
                prefix: &#39;App\Entity&#39;
                alias: App

But I have not found any option to allow the number aware :(

Deprecation: Doctrine\ORM\Mapping\UnderscoreNamingStrategy without making it number aware is deprecated

I am using Doctrine 1.1 in Zend. I am trying to write a query that will return records that have a null value in a certain column.

		$q = Doctrine_Query::create()
		-&gt;select(&#39;a.*&#39;)
		-&gt;from(&#39;RuleSet a&#39;)
        -&gt;where(&#39;a.vertical_id = ?&#39;, null);

		$ruleset_names_result = $q-&gt;execute(array(), Doctrine::HYDRATE_ARRAY);

I have three records in the ruleset table which have a _NULL_ value in the vertical_id column yet the query doest not find these.

Appreciate the help.

Sid.

How to specify null value as filter in a Doctrine query?

How can I get the last insert id with doctrine 2 ORM? I didn&#39;t find this in the documentation of doctrine, is this even possible?

Get the last insert id with doctrine 2?

Let&#39;s say I have entity `$e`. Is there any generic way to store it as another row, which would have the same entity data but another primary key?

Why I need this: I&#39;m implementing some sort of [Temporal Database][1] schema and instead of updating the row I just need to create another one.


  [1]: http://en.wikipedia.org/wiki/Temporal_database

How to re-save the entity as another row in Doctrine 2

What is the difference between the 2 options above? When is it preferable to choose each option? 


Doctrine: cascade=&quot;remove&quot; vs orphanRemoval=true

I want to check my understanding of cascade operations on Doctrine associations. For the purpose of this question, I have two models: `Customer` and `Insuree`.

If I define a many to many relationship between a `Customer` and `Insuree` and set `cascade{&quot;all&quot;}`, I understand that this will:

* Adding a new insuree to a customer will persist this insuree and create an association in the join table.
* Removing an insuree from the collection will detach the insuree from the customer and detach the customer from the insuree.
* Deleting the customer will delete all insurees associated with the customer.

This is the definition of the association on ```Customers```.

    /**
     * @ORM\ManyToMany(targetEntity=&quot;Insuree&quot;, inversedBy=&quot;customers&quot;, cascade={&quot;all&quot;})
     * @ORM\JoinTable(name=&quot;customer_insuree&quot;,
     *      joinColumns={@ORM\JoinColumn(name=&quot;customer_id&quot;, referencedColumnName=&quot;id&quot;)},
     *      inverseJoinColumns={@ORM\JoinColumn(name=&quot;insuree_id&quot;, referencedColumnName=&quot;id&quot;)}
     * )
     */
    protected $insurees;


If I define the inverse many to many relationship between an `Insuree` and `Customer` and set `cascade{&quot;all&quot;}`, I understand that this will:

* Adding a new customer to an insuree will persist this customer and create an association in the join table.
* Removing a customer from the collection will detach the customer from the insuree and detach the insuree from the customer.
* Deleting the insuree will delete all customers associated with it.

This is the definition of the association on ```Insurees```.

    /**
     * @ORM\ManyToMany(targetEntity=&quot;Customer&quot;, mappedBy=&quot;insurees&quot;, cascade={&quot;all&quot;})
     */
    protected $customers;

If I then define the relationship as to cascade on persist, merge and detach - deleting the insuree will not delete all associated customers - it will only remove the associations between the insuree and its customers?

    /**
     * @ORM\ManyToMany(targetEntity=&quot;Customer&quot;, mappedBy=&quot;insurees&quot;, cascade={&quot;persist&quot;, &quot;merge&quot;, &quot;detach&quot;})
     */
    protected $customers;

Understanding Doctrine Cascade Operations

    WHERE a = 1 AND (b = 1 Or b = 2) AND (c = 1 OR c = 2)

How can i make this in Doctrine?

    $q-&gt;where(&quot;a = 1&quot;);
    $q-&gt;andWhere(&quot;b = 1&quot;)
    $q-&gt;orWhere(&quot;b = 2&quot;)
    $q-&gt;andWhere(&quot;c = 1&quot;)
    $q-&gt;orWhere(&quot;d = 2&quot;)

this isnt correctly... Should be:

    $q-&gt;where(&quot;a = 1&quot;);
    $q-&gt;andWhere(&quot;b = 1&quot;)
       $q-&gt;orWhere(&quot;b = 2&quot;)
    $q-&gt;andWhere(&quot;c = 1&quot;)
       $q-&gt;orWhere(&quot;d = 2&quot;)

but how can i make it? In Propel is function **getNewCriterion**, and in Doctrine...?

How to use andWhere and orWhere in Doctrine?

# The error
Cannot delete or update a parent row: a foreign key constraint fails.

# The classes

    class Teacher {

        /**
         *@ORM\OneToMany(targetEntity=&quot;publication&quot;, mappedBy=&quot;teacher&quot;)
         */
        protected $publications;
    }

    class Publication {

        /**
         * @ORM\ManyToOne(targetEntity=&quot;Teacher&quot;, inversedBy=&quot;publications&quot;)
         * @ORM\JoinColumn(name=&quot;teacher_id&quot;, referencedColumnName=&quot;id&quot;)
         */
        protected $teacher;
    }

# I want

What I want is to make it that when you delete a teacher, the id_teacher is modified to NULL. I want to keep the publication but without reference to Professor.

I don&#39;t know how do that in Doctrine, Is it possible? Or always the relationship has to be with a teacher?

Doctrine 2 OneToMany Cascade SET NULL

Can someone tell me how to get all entities of one type which are marked with &quot;EDIT&quot; ACL permission?

I would like to build a query with the Doctrine EntityManager.

Symfony2: how to get all entities of one type which are marked with &quot;EDIT&quot; ACL permission?

What&#39;s the difference between `Doctrine\Common\Persistence\ObjectManager` and `Doctrine\ORM\EntityManager` when using it in a custom form type?

I can get the respository using both `$this-&gt;em-&gt;getRepository()` and `$this-&gt;om-&gt;getRepository()`.

    class MyFormType extends \Symfony\Component\Form\AbstractType
    {

        /**
         * @var Doctrine\ORM\EntityManager
         */
        protected $em;
    
        public function __construct(Doctrine\ORM\EntityManager $em)
        {
            $this-&gt;em = $em;
        }

     }

Instead of:

    class MyFormType extends \Symfony\Component\Form\AbstractType
    {

        /**
         * @var Doctrine\Common\Persistence\ObjectManager
         */
        protected $om;
    
        public function __construct(Doctrine\Common\Persistence\ObjectManager $om)
        {
            $this-&gt;om = $om;
        }

     }

Difference between ObjectManager and EntityManager in Symfony2?

I have a WebTestCase that executes some basic routes in my application.

I want to, on the `setUp` method of PHPUnit, create a test database identical to my main database, and load fixtures into it.

I&#39;m currently doing some workaround and executing some console commands, something like this:

    class FixturesWebTestCase extends WebTestCase
    {
        protected static $application;
    
        protected function setUp()
        {
            self::runCommand(&#39;doctrine:database:create&#39;);
            self::runCommand(&#39;doctrine:schema:update --force&#39;);
            self::runCommand(&#39;doctrine:fixtures:load --purge-with-truncate&#39;);
        }
    
        protected static function runCommand($command)
        {
            $command = sprintf(&#39;%s --quiet&#39;, $command);
    
            return self::getApplication()-&gt;run(new StringInput($command));
        }
    
        protected static function getApplication()
        {
            if (null === self::$application) {
                $client = static::createClient();
    
                self::$application = new Application($client-&gt;getKernel());
                self::$application-&gt;setAutoExit(false);
            }
    
            return self::$application;
        }
    }

But I&#39;m quite sure this is not the best approach, especially because the `doctrine:fixtures:load` expects the user to hit a `Y` char to confirm the action.

How can I solve that?

Best way to create a test database and load fixtures on Symfony 2 WebTestCase?

My first symfony2 project is a list of guests (invited in an event) stored in a database. I have 

 - created the entity class Guest with all variables for them (id, name, address, phone number etc.) 
 - created the schema in the mysql db
 - created a route for &quot;adding a guest&quot; to a twig template
 - created a formType 

and finally a &quot;createGuest&quot; method in the Controller and everything works fine. 

I can&#39;t manage to remove a guest from the database. I have read every tutorial in the web, including the official Symfony2 book; all that it says is :

**Deleting an Object**

*Deleting an object is very similar, but requires a call to the remove() method of the entity manager:*

&lt;!-- language: lang-php --&gt;

    $em-&gt;remove($product);
    $em-&gt;flush();

It does not say anything more than that (even the &quot;Update an object&quot; section is missing documentation) on how to connect the controller deleteAction($id) with the twig template. What I want to do is to list all guests with a viewGuests action and a viewGuests twig template, having a delete icon next to every row, which you should click to delete an entry. Simple, but I cannot find any documentation and do not know where to start from. 

&lt;!-- language: lang-php --&gt;

    public function deleteGuestAction($id)
        {
            $em = $this-&gt;getDoctrine()-&gt;getEntityManager();
    	    $guest = $em-&gt;getRepository(&#39;GuestBundle:Guest&#39;)-&gt;find($id);
    	
    	    if (!$guest) {
    	        throw $this-&gt;createNotFoundException(&#39;No guest found for id &#39;.$id);
    	    }
    	
    	    $em-&gt;remove($guest);
    	    $em-&gt;flush();
    	
    	    return $this-&gt;redirect($this-&gt;generateUrl(&#39;GuestBundle:Page:viewGuests.html.twig&#39;));
        }





How do I delete an entity from symfony2

Is it possible to generate a single entity from database using the Symfony2 console tool?

In the middle of coding I had to add a table and there are modifications made to the existing entity classes. So I don&#39;t want all my entities regenerated. 

Any suggestions will be appreciated!

Generating a single Entity from existing database using symfony2 and doctrine

I am looking for the best way to go about testing the following static method (specifically using a Doctrine Model):

    class Model_User extends Doctrine_Record
    {
        public static function create($userData)
        {
            $newUser = new self();
            $newUser-&gt;fromArray($userData);
            $newUser-&gt;save();
        }
    }

Ideally, I would use a mock object to ensure that `fromArray` (with the supplied user data) and `save` were called, but that&#39;s not possible as the method is static.

Any suggestions?

All Doctrine Solutions on Gang of Coders

Total of 30 Doctrine Solutions