Doctrine 2 - ORM

SchemaTool does not recognize unique constraint

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-ALPHA4
  • Component/s: Tools
  • Security Level: All
  • Labels:
    None
  • Environment:
    MySQL

Description

SchemaTool will attempt to continually add unique contraints to a column. This would seem to be an issue with the way that it calculates the difference between models and the database.

Activity

Ascending order - Click to sort in descending order
Benjamin Eberlei made changes -
Field Original Value New Value
Assignee Roman S. Borschel [ romanb ] Benjamin Eberlei [ beberlei ]
Hide
Permalink
Benjamin Eberlei added a comment -

Fixed with DDC-169.

Show
Benjamin Eberlei added a comment - Fixed with DDC-169 .
Benjamin Eberlei made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Benjamin Eberlei made changes -
Workflow jira [ 10419 ] jira-feedback [ 14169 ]
Benjamin Eberlei made changes -
Workflow jira-feedback [ 14169 ] jira-feedback2 [ 16033 ]
Benjamin Eberlei made changes -
Workflow jira-feedback2 [ 16033 ] jira-feedback3 [ 18286 ]
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
  • Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-148, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Matt Curcio
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: