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

PostgreSqlSchemaManager fails to set foreign key onDelete/Update option properly if table has 'SET NULL' or 'SET DEFAULT' foreign key constraints

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.1.2
    • Component/s: Schema Managers
    • Labels:
      None

      Description

      This table structure:
      CREATE TABLE t1 (id INT NOT NULL, PRIMARY KEY(id));
      CREATE TABLE t2 (id INT NOT NULL, fk_id INT DEFAULT NULL);
      ALTER TABLE t2 ADD FOREIGN KEY (fk_id) REFERENCES t1(id) ON DELETE SET NULL NOT DEFERRABLE INITIALLY IMMEDIATE;

      will cause the listTableForeignKeys to produce incorrect results for the onDelete/Update constraints (the 'DEFAULT' or 'NULL' in 'SET DEFAULT' or 'SET NULL' respectively gets cut off).

      This looks to be fixed in the main branch.

        Activity

        phekmat Payam Hekmat created issue -
        beberlei Benjamin Eberlei made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 2.1.2 [ 10160 ]
        Resolution Fixed [ 1 ]
        beberlei Benjamin Eberlei made changes -
        Workflow jira [ 12922 ] jira-feedback2 [ 17741 ]
        beberlei Benjamin Eberlei made changes -
        Workflow jira-feedback2 [ 17741 ] jira-feedback3 [ 20096 ]

          People

          • Assignee:
            beberlei Benjamin Eberlei
            Reporter:
            phekmat Payam Hekmat
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: