Bug #45397 | Edit table GUI shows the wrong column flags | ||
---|---|---|---|
Submitted: | 9 Jun 2009 11:04 | Modified: | 13 Dec 2012 17:13 |
Reporter: | Karsten Wutzke | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.4a | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | ai, column flags, Edit Table, nn |
[9 Jun 2009 11:04]
Karsten Wutzke
[9 Jun 2009 12:32]
Valeriy Kravchuk
Thank you for the UI changes suggested.
[12 Jun 2009 1:57]
Alfredo Kojima
PK can be toggled by double clicking the 1st column. However I agree that it's non-intuitive and probably very few people know about that. But it does sound like a good idea to redesign the columns list.
[17 Sep 2009 18:59]
Karsten Wutzke
I looked at the 5.2.3a changes. The flags shown should always be in this order: PK | UK | FK | NN | Default 1. UK = unique key is missing. We need this. 2. FK should be shown, all disabled. They're just for information purposes. Like this, you can immediately recognize identifying relationships (where PK and FK are checked). 3. NN should immediately be followed by Default, because you can immediately see if the defaults are correct, which are NULL for nullable columns most of the time. All other flags (BIN, UN, ZF, AI) *should not necessarily be here*! That's because they are *no general* flags. They are *type-dependent* and should go where they used to be: into another area to the right, above the comment. I liked this a lot more. A general request: Please colorize the checkboxes that are functionally disabled! This holds true for all type-dependent and FK checkboxes. These are GUI basics.
[17 Sep 2009 19:25]
Karsten Wutzke
I apologize, but UK should be UQ, because UNIQUE is a constraint, not a key... because of this, you should probably use the order: PK | FK | UQ | NN | Default This looks like the best you can get: PK-FK for identifying relationships, all constraints thereafter (UQ + NN), followed by Default, which is not a constraint, but because of the NULL issues should be placed next to NN.
[15 Oct 2009 6:43]
Susanne Ebrecht
Karsten is right here. Unique is a constraint.
[15 Oct 2009 21:17]
Karsten Wutzke
Two things: 1. I'd very much appreciate if this RFE would make it to 5.2, not 6.0. It is my personal #1 bug report. :-( 2. WB 5.2.4a is already a small improvement, however, it would be nice to have FK next to PK, too, even if these are not togglable. It is a very intuitive element for recognizing identifying and non-identifying relationships. Playing with the PK check marks when seeing FK next to them makes immediately clear what identifying and non-identifying relationships are, without have to read the manual or entering these terms into a search engine. PK | FK | UQ | NN | Default should always show AI | UN | ZF | BIN belong to the "old" *type-specific* box to the right. Note, that AI and a Default value exclude themselves as well (mixing AUTO_INCREMENT and DEFAULT raises an error in MySQL). It doesn't make sense anway.
[2 Nov 2009 12:46]
Karsten Wutzke
I noticed another issue, see here: http://bugs.mysql.com/bug.php?id=48468
[13 Dec 2012 17:13]
Philip Olson
This is an obsolete request, so it is being closed.