Bug #99301 JSON column continually ALTER'd on Synchonise.
Submitted: 18 Apr 2020 23:38 Modified: 25 May 2020 13:53
Reporter: Steven Pearce Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:8.0.19 OS:Any
Assigned to: CPU Architecture:Any
Tags: alter, sync

[18 Apr 2020 23:38] Steven Pearce 
Description:
Simple table with JSON column, keeps getting regenerated

SHOW CREATE TABLE `test`.`response`

returns

CREATE TABLE `response` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `body` json DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

A sync then performs the following changes.

ALTER TABLE `test`.`response` 
CHANGE COLUMN `body` `body` JSON NULL

Once complete a resync, will perform the same changes once again.
This is currently Syncing against MySQL 8.0.18

Could it be the DEFAULT that is causing a problem?

How to repeat:
Will include Test MWB with single table
[18 Apr 2020 23:39] Steven Pearce 
Simple single table Test Case to demonstrate the problem

Attachment: test_json.mwb (application/octet-stream, text), 22.46 KiB.
[18 Apr 2020 23:40] Steven Pearce 
Changed Version
[19 Apr 2020 6:55] MySQL Verification Team 
Hello Steven,

Thank you for the report and feedback.
Verified as described with provided model file on Win10 with WB 8.0.19.

regards,
Umesh
[25 May 2020 13:53] Steven Pearce 
Verified on Win10 so changed OS to 'Any'
[14 Sep 18:05] Omer Barnir 
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.