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.

HeidiSQL have a Serious BUG in PK Auto_Increment

chiaravel's profile image chiaravel posted 1 month ago in General Permalink

Today has been a very unpleasant day, since I work as a DBA and made changes in production that ended badly due to a huge BUG that HeidiSQL has.

If you have a Primary Key configured with Auto_Increment, and then modify the Data Type, changing it to another type ..

Eg change an INT type to MEDIUMINT

HeidiSQL removes the Auto_Increment as a property of the field and leaves a '0' as the DEFAULT value.

all subsequent INSERTs fail when they detect duplicate key.

(I have tested this on all other tools available on the market and none of them give this fault)

And not only that ... any numerical data that you modify, if it does not have a DEFAULT value assigned ... it forces a '0' which is a very big error.

I thought it was because I had version 10.3, but now with the latest version .. still with the error.

Please correct this .. it is very bad.

Thank you

ansgar's profile image ansgar posted 1 month ago Permalink

That sounds like an issue I resolved in a recent nightly build. You may update Heidi to the latest build (not release) and retry.

chiaravel's profile image chiaravel posted 1 month ago Permalink

Hi,

Nice to meet you

How can I do that ? I have the last release and this fails again

Thanks

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.
chiaravel's profile image chiaravel posted 1 month ago Permalink
date/time          : 2020-09-20, 15:23:13, 848ms
computer name      : PCPABLO
user name          : Usuario <admin>
registered owner   : Usuario de Windows
operating system   : Windows 10 x64 build 18363
system language    : Spanish
system up time     : 19 hours 1 minute
program up time    : 674 milliseconds
processors         : 12x AMD Ryzen 5 3600 6-Core Processor
physical memory    : 8161/16315 MB (free/total)
free disk space    : (C:) 39,41 GB
display mode       : 1920x1080, 32 bit
process id         : $8a4
allocated memory   : 61,97 MB
largest free block : 131025,96 GB
executable         : heidisql.exe
compiled with      : Delphi 10.4 Sydney
madExcept version  : 5.0.99
callstack crc      : $9a4f1c6a, $a0dc6595, $a0dc6595
exception number   : 1
exception class    : EAccessViolation
exception message  : Access violation at address 00007FFAFE51AAC9 in module 'KERNELBASE.dll'. Read of address 0000000000000004.

main thread ($aa4):
7ffafe51 KERNELBASE.dll
7ffafe55 KERNELBASE.dll                         VerQueryValueW
00ec7cb3 heidisql.exe   Main           1804 +35 TMainForm.FormCreate
0087ac03 heidisql.exe   Vcl.Forms               TCustomForm.DoCreate
0087a3f9 heidisql.exe   Vcl.Forms               TCustomForm.Create
00a07c8b heidisql.exe   extra_controls   43  +1 TExtForm.Create
0088b466 heidisql.exe   Vcl.Forms               TApplication.CreateForm
00f178f7 heidisql.exe   heidisql         98 +36 initialization
7ffb0097 KERNEL32.DLL                           BaseThreadInitThunk
7ffb013a ntdll.dll                              RtlUserThreadStart
ansgar's profile image ansgar posted 1 month ago Permalink

You removed the version number from the crash report - accidentally?

And in what way is that crash related to the issue you reported above?

chiaravel's profile image chiaravel posted 1 month ago Permalink

This Crash is attempting to upgrade to the last BUILD

ansgar's profile image ansgar posted 1 month ago Permalink

Ok, and on which build did that crash happen?

chiaravel's profile image chiaravel posted 1 month ago Permalink

6097

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.