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.

Query encoding broken after saving

Enissay's profile image Enissay posted 11 months ago in General Permalink

I've been experimenting huge encoding issues since one of the software upgrades around may/june. I have managed to adapt since then, but it's no more bearable.

Here's an example:

Save the follosing in a test.sql file then close it from heidi

SET @test := 5;
SELECT 
    @test+1
;

When reopening it will show up the +1 missing!

SET @test := 5;
SELECT 
    @test
;

If I save it with a space after the + eg: @test+ 1, only the + will disappear:

SET @test := 5;
SELECT 
    @test 1
;

Please advise if there's a fix as it is driving me nuts.

PS: I'm running:

  • Win10 x64
  • Heidi 10.2.0.5728 x64 (I just updated and did the tests in)

Thanks in advance ;-)

ansgar's profile image ansgar posted 11 months ago Permalink

I can reproduce that, but only if I open the file in "UTF-7" encoding:

Description

You should use "UTF-8" instead.

Enissay's profile image Enissay posted 11 months ago Permalink

OMG, was it that simple x_x I was opening files as I used to do for months: I only double click with no default options.

Question is: how come UTF-7 is selected by default and how to make UTF-8 default instead ?

Enissay's profile image Enissay posted 11 months ago Permalink

OMG, apparently all what it takes is to select it once and it remembers it... If Only I have asked this before, I was so lazy to provide an example :x

Thank you ansgar for the fast support

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.