Uploaded image for project: 'Doctrine DBAL'
  1. Doctrine DBAL
  2. DBAL-591

[GH-365] Added existence check before dropping constraints in postgres


    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5, 2.4.2
    • Component/s: None
    • Security Level: All
    • Labels:


      This issue is created automatically through a Github pull request on behalf of stefk:

      Url: https://github.com/doctrine/dbal/pull/365


      The Schema object generates distinct sql queries for altering a table and for removing a constraint or an index. However, in some cases, the `drop` query may come after an `alter table` query deleting the column to which the index/constraint was bound. In postgres, where dropping a column automatically drops its attached indexes and constraints, executing the queries in that order leads to an sql error (trying to drop something that has already been deleted -> "SQLSTATE[42704]: Undefined object").

      This PR introduces a quick fix for that issue (not sure it's the best way though).

        Issue Links


          doctrinebot Doctrine Bot created issue -
          beberlei Benjamin Eberlei made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 2.5 [ 10523 ]
          Fix Version/s 2.4.2 [ 10620 ]
          Resolution Fixed [ 1 ]
          beberlei Benjamin Eberlei made changes -
          Link This issue is duplicated by DBAL-584 [ DBAL-584 ]


            • Assignee:
              beberlei Benjamin Eberlei
              doctrinebot Doctrine Bot
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: