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.

File Import Setting

sam_benne's profile image sam_benne posted 6 months ago in Feature discussion Permalink

Currently when doing a import the default value for the encoding is Auto Detect, this always seems to fail and leaves a lot of broken symbols in the content. However, changing this to UTF-8 means the import works.

What would be nice in the preferences is somewhere that you can set the default value of this. It then means that we can set this across servers and not have someone forget and then cause problems later down the line.

ansgar's profile image ansgar posted 6 months ago Permalink

The current release already warns when you are about to use the auto-detection:

Description

Also, HeidiSQL remembers the last used encoding when you load another file.

lotiara's profile image lotiara posted 2 months ago Permalink

Hi when I use "client parse file contents" I cannot specify UTF-8 and omly does a partial import(strange results. If I set "server parse" I can specify UTF-8 and then works correctly. Why cant I specify encoding with Client parses file option ? Thanks

ansgar's profile image ansgar posted 2 months ago Permalink

The "Client" method does not need an additional encoding selector, because you already selected the encoding in the file-open dialog. The "client" method uses the connection's charset for the generated INSERT commands.

Description

The dropdown is for the "server" method only, to support the charset clause in the generated LOAD DATA command.

lotiara's profile image lotiara posted 2 months ago Permalink

Hi, Hadn't noticed that. Thank you

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




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.