I was looking at trigger creation - db does not let save it unless tables & field names are correct.
With no problem, it let you rename columns , which then makes trigger unusable, no warning at all too.
Further I think it deletes automaticaly table related trigger as table gets droped, no warning again if trigger is related to another table but it contains truncated table in code.
Well, I guess this cross check will not be in HeidiSQL, but mybe ...
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.