Doctrine DBAL

schema-tool creates primary keys as unique constraints

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.5
  • Fix Version/s: 2.0.7, 2.1
  • Component/s: None
  • Labels:
    None

Description

The schema tool calls AbstractPlatform::getCreateIndexSQL() to create new indexes. When the index is primary, this creates a unique key instead.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Karsten Dambekalns added a comment -

While the description here is very sparse, I think it is about the following problem.

When a primary key is to be created for MySQL, the statement generated is

ADD UNIQUE INDEX PRIMARY ON foo (bar)

This fails with MySQL stating primary is an invalid name. Since "ADD INDEX" is mapped to "ALTER TABLE" anyway, I just made that

ALTER TABLE foo ADD PRIMARY KEY (bar)

which works fine. Also

DROP INDEX primary ON foo

doesn't work, unless I quote primary (since it is a reserved word), but there

ALTER TABLE foo DROP PRIMARY KEY

seems better as well.

Show
Karsten Dambekalns added a comment - While the description here is very sparse, I think it is about the following problem. When a primary key is to be created for MySQL, the statement generated is ADD UNIQUE INDEX PRIMARY ON foo (bar) This fails with MySQL stating primary is an invalid name. Since "ADD INDEX" is mapped to "ALTER TABLE" anyway, I just made that ALTER TABLE foo ADD PRIMARY KEY (bar) which works fine. Also DROP INDEX primary ON foo doesn't work, unless I quote primary (since it is a reserved word), but there ALTER TABLE foo DROP PRIMARY KEY seems better as well.
Hide
Permalink
Benjamin Eberlei added a comment -

Fixed

Show
Benjamin Eberlei added a comment - Fixed

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    arnaud-lb
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: