MySQL Bugs: #44017: Relation endpoint changes not cascading

Bug #44017	Relation endpoint changes not cascading
Submitted:	1 Apr 2009 17:45	Modified:	20 Oct 2009 11:09
Reporter:	Ken Brown	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.9	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	cascade, change, CHECKED, column, refactoring, workbench

Description:
when a column name is changed and relations utilise the column the change is not cascaded to the children when change applied at parent

How to repeat:
create table 1 with column aaa
create table 2 with column bbb
create parent/child on table 1/2
change table 1.column aaa to column ccc
table 2 shill shows column aaa

Suggested fix:
None

This also applies to the flags - while this is not that important as the constraint will check like for like the flags should still cascade.  May have a performance impact depending on whether flags are checked before the relation is honored.

Thank you for the problem report.

Hello Ken,

could you provide more info on that? Do you mean the datatypes/Flags like here http://bugs.mysql.com/bug.php?id=38801 or are you talking about the column names?

BR
tax

both - I would have though that when a field is defined it becomes an object and when use inheritance rules would apply.

This would all b e a lot easier if the tool supported full object palets

I had verified it in case of column names. (Automatically added) FK column name does NOT change accordingly to the change of column name it refers to.

This is part of a refactoring feature. The "child" and "parent" columns are separate objects and cascading changes without proper review and confirmation by user can lead to unexpected results in complex models.

so you are saying inconsistent columns are better than consistent ones at relationship endpoints.  I've worked with some big models in my time (+ 5k tables) and I have never wanted inconsistent metadata in anything I've built.  Expecting users to check all the children when changing a parent IMHO is not an acceptable practice and does not happen in ERWIN, SQL DESIGNER and EMBARCADERRO to name 3.
Surely putting the columns in metadata and using this to build the model is a much better approach with all the uses linked back to the metadata to global changes can be readily applied is the sensible way forward.
If you don't want to go that way you could always approach CA and the others and offer to build a connection engine for mysql instead

Many thanks for writing a feature request.

After long discussion we decided that we won't change this behaviour in foreseeable future.

Thank you for your interests in MySQL Workbench.