Wrong Charset in Import

Hi Ansgar and forum users,

yesterday I made an export of one table (as usual) using your export possibility in HSQL.

I opened the sql file (N++) and see utf-8, all fine (german umlauts) ... great!

I drag'n'drop the file into Heidi (for import) and have crap on the umlauts.

I tried "open sql file" and it is the same, but a dialog appears about "auto identification of charset". Using "auto detection" if fails; discarding leads to nothing.

This happens first after upgrading to 11.2 and - with the new update (for me) today - it's still present, so this is the small info into your direction.

More info:

• export made with HeidiSQL Version: 11.2.0.6213
• tried import the same
• current version .6214 and same behaviour on importing

The attached picture shows the exported sql with one random dataset and the right interpretation of the german umlaut. The other half show the wrong import in HSQL.

Using your exported file as dump on the shell, everything is fine in the table.

Urgent? No, not really (workaround "shell" is fine for the moment).

Other possibility: new settings in HSQL and I haven't seen/made them?

Please read the warning dialog about auto-detection, and select the right encoding in the file-open-dialog.

Ok, but ...

... Menu > File > sql open (CTRL + O) is the same like selecting the file from right click into request tab.

And both result in this dialog (attachement).

Yes, and in both cases you see an encoding drop-down in the file-open dialog, which you should change from "Auto-detect" to "UTF-8" e.g.

Ah, sorry, you won't see that dialog of course if you drop a file into the editor. That should probably be considered.

Check, thanks, tested and solved.