Doctrine 2 association without foreign key constraints

14,241

Solution 1

I had to go through the same process recently and fortunately there is an easy solution, just add nullable=true to the column's annotation.

This will work as long as the existing data is valid, in my case I had to change 0's to NULL's and change keys that didn't exist anymore to NULL.

Solution 2

Basically you can't prevent the sql commands from being generated. At least not without diving into the Doctrine code.

However, you don't need to actually apply the constraints to your database. D2 will work just fine without them.

Share:
14,241
chiborg
Author by

chiborg

Updated on June 05, 2022

Comments

  • chiborg
    chiborg almost 2 years

    I'm in the process of converting a legacy PHP application to Symfony 2. The application data is not very consistent at the moment, so I would like to avoid creating foreign key constraints. I have the following annotation in my "Product" entity class:

    class Product {
    
      // some definitions
    
      /**
       * @ORM\ManyToOne(targetEntity="Manufacturer")
       * @ORM\JoinColumn(name="manufacturer_id", referencedColumnName="id" )
       */
      private $Manufacturer;
    }
    

    When I do app/console doctrine:schema:update, I get the SQL command

     ALTER TABLE products ADD CONSTRAINT FK_F6FA18741C3BF575 
       FOREIGN KEY (manufacturer_id) REFERENCES manufacturer(id);
    

    How can I avoid this?