Bug #51462 | Command "Delete selected column" can be misunderstood | ||
---|---|---|---|
Submitted: | 24 Feb 2010 15:32 | Modified: | 16 Nov 2010 10:36 |
Reporter: | Thomas Hummes | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.16b | OS: | Windows (7) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | Localisation |
[24 Feb 2010 15:32]
Thomas Hummes
[26 Feb 2010 17:55]
Valeriy Kravchuk
Thank you for the problem report.
[26 Feb 2010 21:41]
Johannes Taxacher
You may already be aware that "row" in that case refers to the "row of columns" displayed in the column editor. But we my rephrase that to avoid such confusion. Thanks for pointing that out.
[1 Oct 2010 2:51]
Alfredo Kojima
I think "Delete selected rows" will be even more confusing to people familiar with DB terminology. I would vote to leave things as they are, the header of the columns list even says Column Name in it and the tab says Columns.
[16 Nov 2010 10:36]
Mike Lischke
Naturally there is a small conflict between the fact we are editing table columns and their representation as rows in the column editor. However, as Alfredo pointed out, the term "column" is the correct one in this context as it refers to the object being manipulated not its representation. Alternatively the term "attribute" could be used (which would be the correct term seen from relational algebra), thought that is probably by far not as common as "column". So consequently, the naming will not be changed.