Doctrine 2 - ORM

Switching owning side of Many2Many generates broken SQL of DROP INDEX

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Tools
  • Security Level: All
  • Labels:
    None

Description

When switching owning side of a many2many bi-directional association, it produces this type of SQL to be executed:

DROP INDEX primary ON CompanyEntity_CompanyEmailDomain;
CREATE UNIQUE INDEX primary ON CompanyEntity_CompanyEmailDomain (emaildomain_id, company_id)

The problem is that "primary" is a reserved keyword in MySQL.
It should be quoted. =)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Eberlei added a comment -

The problem is that its a primary key and should be dropped using the appropriate syntax. And not created as a unique one aswell.

Show
Benjamin Eberlei added a comment - The problem is that its a primary key and should be dropped using the appropriate syntax. And not created as a unique one aswell.
Hide
Permalink
Benjamin Eberlei added a comment -

MySQL platform already guards against this since ~1 year.

Show
Benjamin Eberlei added a comment - MySQL platform already guards against this since ~1 year.

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Guilherme Blanco
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: