crash on edit in mssql

[expired user #7787]'s profile image [expired user #7787] posted 10 years ago in General Permalink
While editing single cell:

press "F2" to edit cell content
change the content and press ENTER

After pressing Enter Heidi suddenly turns off, i don't get any error message.
ansgar's profile image ansgar posted 10 years ago Permalink
Is that reproducible or was it a one-time error?
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
this error ocured every time, now i notice that it happen also in MYSQL databases while editing cell value, after pressing ENTER Heidi turns off without any message...
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
in previous versions everything was OK, but i don't know which last one was good :(
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
heidi exits even when no changes where made in cell.

My colegue has Heidi: 8.1.0.4545 and he can edit cell values without any problems.
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
Update 4714 didn't solve this problem. :(
ansgar's profile image ansgar posted 10 years ago Permalink
So, again, you are in the "Data" tab, and when editing a text value (or date, number...?) in the grid inplace editor, and pressing Enter lets HeidiSQL crash?
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
yes, but wht i've noticed it only happens onWindows XP, on windows 7 everything is ok
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
I've downloaded again from your website version 4694 and it's bug free, after update from menu help to 4714 it is crashing again. So I'll stay with 4694 version
ansgar's profile image ansgar posted 10 years ago Permalink
Hmm ok, XP may be an explanation. I have no xp system any longer to use for testing purposes. Any chance you upgrade to windows 7?
jfalch's profile image jfalch posted 10 years ago Permalink
i´m on xp too, with very little chance of upgrade. could provide a "clean XP" vm...
[expired user #7787]'s profile image [expired user #7787] posted 10 years ago Permalink
"Any chance you upgrade to windows 7?"

but it's not a sollution, what had change since version 4694 and now it's crushing on cell editing event. there are some chance to switch to win7 but not in the closest future. Heidi is very usfull tool and i would like to use it on systems that you declare that it's working fine :)

HeidiSQL runs fine on Windows (XP, Vista, 7, 8)
ansgar's profile image ansgar posted 10 years ago Permalink
Yes, of course, I would like to keep Heidi compatible with XP. I only have no clue why it shuts down so silently for you. Could be that it's only on your computer, probably your colleage can try the current build?
[expired user #6457]'s profile image [expired user #6457] posted 10 years ago Permalink
I'm on XP also and just noticed the same problem today, I was on 8.3.0.4711, updated to 4714 and it still happens, you can edit the contents as long as you click outside the current record to trigger the update, if you hit the enter key HeidiSQL closes.
[expired user #6457]'s profile image [expired user #6457] posted 10 years ago Permalink
Just downloading the compiled exe, 4709 does NOT have this problem 4710 does.
[expired user #7806]'s profile image [expired user #7806] posted 10 years ago Permalink
Same issue here even after updating to 8.3.0.4714 on XP SP3.

While editing a cell value in a results window if I press ENTER it closes immediately. If I edit a cell value but then click to a different row using the mouse it performs the DB update successfully. This happens on varchar, text, tinyint(1), but does not happen on datetime
field.
ansgar's profile image ansgar posted 10 years ago Permalink
I'm just creating an XP image in VirtualXP, so I have an environment for testing this issue.
ansgar's profile image ansgar posted 10 years ago Permalink
Hm, on XP SP2, I am unable to reproduce that Enter issue.
ansgar's profile image ansgar posted 10 years ago Permalink
"Virtual PC", not "Virtual XP"...
[expired user #7806]'s profile image [expired user #7806] posted 10 years ago Permalink
This may not always happen then a column is edited the first time. For example:

1) Edit an int column by pressing "Enter", typing a number like 3, then pressing "Enter"
2) navigate to a new row and do the same to a column in that row.
3) Navigate back to the row edited in step 1 by pressing "Enter", typing in a number like 2, then pressing "Enter"
4) at that point HeidiSQL immediately closes (no warnings, etc).

I just tested this with 8.3.0.4716
[expired user #7806]'s profile image [expired user #7806] posted 10 years ago Permalink
step 3 should be:

3) Navigate back to the row edited in step 1 and edit the value by pressing "Enter", typing in a number like 2, then pressing "Enter"
ansgar's profile image ansgar posted 10 years ago Permalink
Is it right that this only happens in MSSQL mode? On MySQL, I cannot reproduce it - I've done exactly what you wrote.
ansgar's profile image ansgar posted 10 years ago Permalink
Even on MSSQL and XP, I cannot reproduce this crash. I can't help it - it seems there is some more going on in your machine.
[expired user #7806]'s profile image [expired user #7806] posted 10 years ago Permalink
In my case it happens with Percona Server 5.5.16 with XtraDB (GPL), Release rel22.0, Revision 189

I have the exact same HeideiSQL version on Windows 7 SP1 and don't have the problem there. If it helps, I am running both W7 and XP SP3 in Vmware Fusion on a Mac and nothing has changed in my current configuration in over two years. HeidiSQL hasn't had this particular problem until the past month or so, abou tthe same time that everyone else started experiencing the same issue.
[expired user #7806]'s profile image [expired user #7806] posted 10 years ago Permalink
I've narrowed this down to a change that occurred between 4705 and 4706. I can't reproduce in 4705 but it always happens in 4706.
ansgar's profile image ansgar posted 10 years ago Permalink
r4706 was reverted in r4709, so does it also happen in the current build (4719)?
[expired user #6457]'s profile image [expired user #6457] posted 10 years ago Permalink
I just downloaded just heidisql32.r4719.exe, did not run the installer and yes it still happens.
Win XP pro version 2002
Service Pack 3
Mysql 5.0.45
ansgar's profile image ansgar posted 10 years ago Permalink
That sounds random somehow. r4706 was reverted and it modified anyway nothing with grid editing, but with query parameter binding. I am not able to track it down to anything. Shit.
[expired user #6457]'s profile image [expired user #6457] posted 10 years ago Permalink
This is not fixed in 4761, back to 4709.
[expired user #8047]'s profile image [expired user #8047] posted 10 years ago Permalink
ansgar, you said "Hm, on XP SP2, I am unable to reproduce that Enter issue."

The problem seems to be with the XP SP3, since from a clean install I can reproduce the bug, for example with the last http://code.google.com/p/heidisql/source/detail?r=4767.

If for some reason you can not install XP SP3, let me know and I will send you (by Drive or Dropbox) the hard disk file (.vdi) for Virtualbox that I have prepared for testing.

The only problem is that the XP SP3 installation is in Spanish :)
ansgar's profile image ansgar posted 10 years ago Permalink
Sorry, that was a typo, it is indeed an XP SP3 which I have, not SP2.
[expired user #8047]'s profile image [expired user #8047] posted 10 years ago Permalink
I uploaded the virtual machine file (.vdi) of an XP SP3 (where you can reproduce the problem) to Google Drive, compressed into ZIP.

It is a clean install of XP SP3 in Spanish, and the machine has been created using Virtualbox 3.2.8 (although you can use any other version of Virtualbox) and the virtual machine configuration by default.

In it I have installed the latest version of XAMPP, I created a database called "heidisql" and a table with an auto_increment field and a varchar field.

By going to add a record on varchar field and press enter, you will see how the application closes without giving any notice.

The link

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