Bug #88777 set default value
Submitted: 6 Dec 2017 9:36 Modified: 11 Dec 2017 11:55
Reporter: Karel Kühpast Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:6.3.10 OS:Microsoft Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[6 Dec 2017 9:36] Karel Kühpast
Description:
When I use the TINYINT(1) datatype, the default value for the click will offer „Default 0“, when I use the BOOL datatype (defined as TINYINT(1)) „Default 0“ is not available

How to repeat:
always
[6 Dec 2017 12:20] MySQL Verification Team
Please attach screen-shots for both type, try version 6.3.10 also. Thanks.
[6 Dec 2017 13:00] Karel Kühpast
6.3.6 bulid 511 TINYINT(1)

Attachment: tinyint.jpg (image/jpeg, text), 83.37 KiB.

[6 Dec 2017 13:01] Karel Kühpast
6.3.6 bulid 511 BOOL

Attachment: bool.jpg (image/jpeg, text), 80.85 KiB.

[6 Dec 2017 13:09] Karel Kühpast
On 6.3.10 the same.
[6 Dec 2017 13:30] Karel Kühpast
And if is set Not Null, then Default NULL should not be.
[6 Dec 2017 13:31] Karel Kühpast
is set Not Null

Attachment: notnull.jpg (image/jpeg, text), 194.54 KiB.

[7 Dec 2017 9:50] Chiranjeevi Battula
Hello Karel Kühpast,

Thank you for the bug report.
It is Not a Bug, It is showing available default value options.

Thanks,
Chiranjeevi.
[7 Dec 2017 9:51] Chiranjeevi Battula
Screenshot

Attachment: Bug_88777.png (image/png, text), 104.58 KiB.

[7 Dec 2017 10:04] Karel Kühpast
Hello Chiranjeevi Battula,
but for BOLL should display 0 and it is not there.
[7 Dec 2017 13:00] Karel Kühpast
Hello Chiranjeevi Battula,
but for BOLL should display 0 and it is not there.
[11 Dec 2017 11:55] Chiranjeevi Battula
Hello Karel Kühpast,

Thank you for the feedback.
Verified this behavior on MySQL Workbench in 6.3.10 version.

Thanks,
Chiranjeevi.