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.
- export made with HeidiSQL Version: 22.214.171.12413
- 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?