Bug #35800 update connection-style (solid/dashed) when changing corresp. column

Submitted: 3 Apr 2008 13:36 Modified: 10 May 2008 23:58
Reporter: Johannes Taxacher Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.0.16 OS:Windows
Assigned to: Alfredo Kojima CPU Architecture:Any

[3 Apr 2008 13:36] Johannes Taxacher
Description:
when a column, which references another col via FK, is added/removed from PK the line-style (solid/dashed) should be updated in the diagram accordingly (identifying/non-identifying)

How to repeat:
- import/create two tables like these:

CREATE  TABLE IF NOT EXISTS `table1` (
  `idtable1` INT NOT NULL ,
  PRIMARY KEY (`idtable1`) )
ENGINE = InnoDB;

CREATE  TABLE IF NOT EXISTS `table2` (
  `idtable2` INT NOT NULL ,
  `table1_idtable1` INT NULL ,
  PRIMARY KEY (`idtable2`) ,
  INDEX fk_table2_table1 (`table1_idtable1` ASC) ,
  CONSTRAINT `fk_table2_table1`
    FOREIGN KEY (`table1_idtable1` )
    REFERENCES `table1` (`idtable1` )
    ON DELETE NO ACTION
    ON UPDATE NO ACTION)
ENGINE = InnoDB;

- put the tables on a diagram.
- open table2 and add column `table1_idtable1` to the PK

now the connection-line between the tables should switch to solid as this is an 'identifying relation' then. and switch back to dashed when the column is removed from PK again.
[3 Apr 2008 13:38] Johannes Taxacher
workaround in the meantime: after changing the columns, remove one of the tables from diagram (without removing them from model!) and put it back in from catalog pane. then the lines ar re-created with correct style.
[8 Apr 2008 16:04] Johannes Taxacher
this works now (tested in SVN 3005)
[10 May 2008 23:58] Paul DuBois
Noted in 5.0.18 changelog.

The status of a connection line in a table diagram was not updated
when a foreign key relationship between tables was changed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.