Bug #64830 Wrong minimum cardinality in Model -> Relationship notation -> Classic
Submitted: 1 Apr 2012 13:25 Modified: 13 Aug 2012 23:31
Reporter: r g Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.38 CE OS:Any
Assigned to: CPU Architecture:Any
Tags: cardinality, classic, minimum, model

[1 Apr 2012 13:25] r g 
Description:
The minimum cardinality in the classic view is wrong. It wil now always daysplay that the minimum is one.
But when the foreignkey allows NULL the minimum cardinality should by displayed as 0..* of just 0 and not the 1..* because it could not excist
 

How to repeat:
Make two tables. Allow one table to have an foreign key column allow null.

Suggested fix:
0..* or just 0 depending on the structure.
[1 Apr 2012 14:14] Valeriy Kravchuk 
Model that demonstrates the problem

Attachment: bug64830.mwb (application/octet-stream, text), 5.92 KiB.
[1 Apr 2012 14:15] Valeriy Kravchuk 
Thank you for the problem report. Verified on Mac OS X (see model attached).
[13 Aug 2012 23:31] Alfredo Kojima 
This is not a bug, the notation is just inverted from what you are expecting.
If the FK column allows NULL, it means the referenced object can have 0 or 1 instances. That is shown next to the *referenced* table.