Bug #94650 SQL Scripts Attached on a Model does not sync
Submitted: 14 Mar 2019 5:53 Modified: 28 Jun 2019 8:37
Reporter: Jose Escobar Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:8.0.15, 8.0.16 OS:Windows (Microsoft Windows 10 Home Single Language)
Assigned to: CPU Architecture:x86
Tags: WBBugReporter

[14 Mar 2019 5:53] Jose Escobar 
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\war_a\AppData\Roaming\MySQL\Workbench\log\wb.log]

if you create and attach a SQL Script on a Model, this one does not sync with the 
target database even if you choose "Synchronization: After DDL or Bottom Script"
or "Include SQL Scripts Attached to Model" on "Set Options for Synchronization Script"

How to repeat:
1: Create a Simple Model
2: Create a Simple Script attached on the Model
2a: Select Synchronization: After DDL or Bottom of Script
3: Synchronize Model
3a: Setup your Sync
3b: Check-in: Include SQL Scripts Attached to Model option
3c: Sync
4 Check that the scrip was not executed
 

Suggested fix:
Check the list box "Synchronization" (Located in the right-top of the window after you modify your script) if it is working because if you select whatever option you decided and you close it and reopen that script, you can see that the list box option showed is "Do not include".

Maybe this is why the scripts do not sync on the target database because it does not matter you selection always is 'Do not include'
[28 Jun 2019 8:37] MySQL Verification Team 
Hello Jose Escobar,

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

regards,
Umesh
[14 Sep 18:04] 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.