Default encoding for externally loaded dumps

[brezanac]

Any chance you might reconsider your decision on this?

It's been requested countless times on these forums during the last 5+ years and it keeps being declined on an assumption that the File -> Open option is the only way to load an external SQL file into dbForge.

The issue happens if the SQL file is opened by double clicking on it which results in automatically invoking the default operating system encoding (like Windows1252) without even the option to choose the encoding like in the File-> Open dialog. I don't have to explain how many problems this can cause, from invalid schemas, to corrupt data, unnecessary data synchronizations etc.

The solution should be very simple: add a default encoding setting in the options which will be always used during external SQL file loading unless it's overridden in the File->Open dialog.

P.S. Relying on BOM character to identify encoding for UTF8 dumps is completely wrong since MySQL doesn't support that kind of behavior.

[alexa]

We will investigate this issue and will answer you as soon as possible.

[alexa]

We do apologize for the delay on this.

Could you please send us the file you are experiencing the issue with for investigation?

You can send a reply straight to our support system at supportATdevartDOTcom and alexaATdevartDOTcom.