MySQL Bugs: #32956: uncommon FK terminology such as "Source", "referred"

Bug #32956	uncommon FK terminology such as "Source", "referred"
Submitted:	4 Dec 2007 12:36	Modified:	6 Dec 2007 1:53
Reporter:	Roland Bouman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.10 OSS Beta	OS:	Windows (XP home)
Assigned to:		CPU Architecture:	Any

Description:
WB uses uncommon (IMO unintuitive) terminology to denote aspects of foreign keys. Terms:

"Source Table" / Columns
"Referred Table" / Columns

appear in the "wizard" when the "Pick columns" option is used.

In the table editor, the terms are 
"Foreign Key Table" and "Referenced Table" and this is good as it corresponds directly with the keywords in the DDL syntax:

...FOREIGN KEY .... REFERENCES

How to repeat:
On toolbar, click relationship icon, then on the main toolbar, click the "Pick columns checkox", then, see the wizard text

Suggested fix:
Change "Source" to "Foreign Key" and "referred" to "Referenced"

Thank you for a problem report.

I like to add that it is not really clear what the checkboxes "Start is Optional" and "End is Optional" do. What is the start? what is the end?

Personally I'd like it much better if we'd get three toggle buttons in the relationship toolbar that are always visible. You could use Icons on these to clarify the meaning - the 
"fk table end" button could have a 
 
 o
/|\

Icon and the "puk table end" button could have a 

 o
---

icon and it would be much clearer what is intended.

More terminology issues...in the relationship editor - the one you get when right clicking a relationship > edit relationship, there is a littel fieldset "Integrity constraints". 

The checkboxes there are titled: "Entity Mandatory" and "Referred Entity Mandatory". This does not seem to make sense as we're editing a foreign key. That is, this mixes terminology from a conceptual model ("Entity") with a thing that comes out of a relational data model (it's a foreign key defined on *tables* not entities)

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html