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.

View SQL Security Definer on export.

ameeno's profile image ameeno posted 2 months ago in General Permalink

When exporting to sql, HeidiSQL exports the security definer as dbusername@%.

This causes problems when importing into a different system with a different database username.

My workaround is to download the sql as a file, and hand modify the SQL definers to be CURRENT_USER() instead.

Would it be possible for heidisql to automatically convert dbusername@% to CURRENT_USER when exporting? this would enable me to import directly into the second database on another server using the [SQL export feature]??

ansgar's profile image ansgar posted 2 months ago Permalink

This was reported in the bugtracker in issue #88 . I just put that onto the roadmap for the next release.

Please login to leave a reply, or register at first.