Bug #39514 Can't set attribute "primary" to a key

• Submitted: 18 Sep 2008 9:10
• Modified: 30 Oct 2008 20:14
• Reporter: Fabien Haddadi
• Status: No Feedback
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.0.25
• OS: Windows
• CPU Architecture: Any

[18 Sep 2008 9:10] Fabien Haddadi

Description:
I can't set the PRIMARY attribute to a key that has been defined as a dual column key.

It suggests it, but falls back to the UNIQUE option.

Other attributes are still available, like INDEX.

Setting PRIMARY on dual column keys may work on other tables of the same schema.

How to repeat:
Load the source provided as an attachment.

Edit the z_selection_produit table

Go to the "Indexes" tab.

Try to define the index named PRIMARY as PRIMARY, as per screenshot.

[18 Sep 2008 9:10] Fabien Haddadi

screenshot

Attachment: bug_mysql_wb2.jpg (image/jpeg, text), 129.01 KiB.

[25 Sep 2008 3:51] Valeriy Kravchuk

Thank you for a bug report. Verified just as described.

[30 Sep 2008 20:14] Johannes Taxacher

This is done automatically by workbench when you set the according colums to be PK  (either by double clicking the diamond icon next to the column name or by checking the PRIMARY-Flag in the Flags listbox). To avoid creating duplicate PRIMARY indexes we don't allow setting an index type to PRIMARY directly.
So I assume it's better to remove the entry PRIMARY from the Dropdownbox of Inex-Types (to avoid confusion).

[1 Nov 2008 0:10] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".