mysql - Possible bug with Workbench model synchronization/Forward Engineer? -


i have updated databases model file many times, now, when attempt forward engineer model existing database, or synchronize database, seems tables have triggers associated them (a new thing us) not updated. forward engineering nothing these tables, , in synchronization, there no arrow indicating change detected (there added fields). has else run this? i've wracked net trying find answer. have workaround, it's lot of of work.

an example here: table tbl_wbselements has added fields, workbench isn't spotting them. seems happen tables have triggers; tables without triggers, sps, views, new tables seem foreng , synchronize fine.

this has been solved; pure coincidence several tables triggers affected. problem table designer had added several foreign-key fields tables , left default value of "not nullable" set; so, when workbench tried insert field, found there existing records in foreign table, , couldn't leave field null, skipped new field.

i'd see workbench give sort of warning when happens, took 2 days of investigation sort out (and discovered accident). i'm sure others have been caught type of thing well.


Comments

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -