MySQL Bugs: #95578: Generated Columns do not support UNSIGNED

Bug #95578	Generated Columns do not support UNSIGNED
Submitted:	30 May 2019 15:18	Modified:	31 May 2019 6:38
Reporter:	Vasil Rangelov	Email Updates:
Status:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.16	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	generated column, UNSIGNED

Description:
This is similar to https://bugs.mysql.com/bug.php?id=80988 , except that the problem is with the UNSIGNED flag on integer generated columns.

And in my use case, I need it to match, because I have a stored generated column that is a foreign key, and the referenced column is an unsigned integer.

I've only tested forward engineering from a model, but I would guess that reverse engineering and syncing will have the same problem.

How to repeat:
1. Create a new model.

2. Add a new table with a generated INT column.

3. Tick the UN column in the GUI to make it unsigned.

4. Forward Engineer, and notice that the statement produced does not include UNSIGNED, even though it should.

Suggested fix:
MySQL Workbench should generate "UNSIGNED" in the produced SQL statement if the column is unsigned.

Hello Vasil Rangelov,

Thank you for the report and steps.
Verified as described on Win10 with WB 8.0.16.

regards,
Umesh

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.