DDC-1603: Unique key name isn't correctly set #2242

Closed
doctrinebot opened this Issue Jan 16, 2012 · 5 comments

2 participants

@doctrinebot

Jira issue originally created by user armetiz:

Example :




This will create :
CREATE UNIQUE INDEX UNIQ_6C3BF144F286BC32 ON shows (permalink);
CREATE UNIQUE INDEX 1 ON shows (code);

instead of :
CREATE UNIQUE INDEX UNIQ_6C3BF144F286BC32 ON shows (permalink);
CREATE UNIQUE INDEX UNIQ_6C3BF14477153098 ON shows (code);

The problem comme from SchemaTool, and the first key is a valid result because of "==" instead of "===" inside Table.php.

I have create a PR on Github.

@doctrinebot

Comment created by armetiz:

Here the PR for the ORM SchemaTool : #261
Here the PR for the DBAL Table : doctrine/dbal#94

@doctrinebot

Comment created by @guilhermeblanco:

Merged 2bb5115

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot

Comment created by @beberlei:

DBAL merged back into 2.2 and 2.1.x

@doctrinebot

Comment created by @beberlei:

and Merged into 2.2 and 2.1.x ORM

@doctrinebot doctrinebot added this to the 2.1.6 milestone Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment