Import SQL

A
1.In explorer/open sql file with HSQL
2. It says it is big / want to open directy / no loading into editor
3. Problem: The encoding of file did not get recognized, hence strange characters are getting into db, duplicate key violation, etc. Although sql file is perfectly OK.

B
1.Inside HSQL:
Import/load sql file ---> window with dropdown pops up, with manual encoding settings.

The same thing should be under A somewhere.

Open from within HeidiSQL, rather than Windows explorer. The program's dialogue allows to pick an encoding.

Either go to "Tools-> Load SQL file" or click the appropriate button in the toolbar.

Point beeing: once user gets used to do it from explorer , and bump against 'not readable encoding', user wastes a lot of time to convert encoding with various things, of which none works.

Heidi has a solution, but is kind of hidden.

"normal" UTF-8 or Latin1 files should get auto-detected correctly. I wonder why it does not detect your file encoding already.

The thing was transported over the net , around the corners. But that kind of thing was obviously detected by you also. As it is said , opening .sql from within heidi: Encoing: Autodetect(may fail).

"Tools-> Load SQL file"

This no longer appears in v9 of Heidi, is there a replacement for this ?

thanks

Yes, this menu item was moved to File : Load SQL file