Originally created by: SuperNiFF@gmail.com
What steps will reproduce the problem?
1. Edit a field in the Data tab
2. Press up or down to go to the next row
3. Press F5
What is the expected output? What do you see instead?
I expect the changes to be posted. Instead I see the old value.
In the Log tab I only see a line added like this: 'SELECT COUNT(*) FROM
`tablename`'
What version of the product are you using? On what operating system?
HeidiSQL 3.2 + nightly build 1602
Windows XP Professional (EN)
MySQL 4.0.20 (Redhat Linux)
The database uses innodb
Please provide any additional information below.
This might be important:
When I connect to 5.0.27 version of this same database (instead of
4.0.20), this does not occur.
There I see this line added to the log as expected:
UPDATE `tablename` SET `field`='newvalue' WHERE `key`=x
I've tried it on several tables, different column types, and i've
restarted HeidiSQL, without any effect.
I've tried editing the 4.0.20 database with another client, and that
worked without any problems.
Until recently, I've only had this problem with memo-fields, and INT
fields worked as expected. This has been introduced recently.
Could this have something to do with the used character set?
The 5.0 database uses utf8, and I think that's not supported on 4.0.
There are no other (intentional) differences between the 2 databases.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
No clue what the cause is here. But it should get fixed along with switching to
VirtualTree for the grid component.
Labels: -Priority-Medium Severity-Broken
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: SuperNiFF@gmail.com
Ok, some additional information here.
The bug description suggests that updates are not processed, but inserts don't work
either.
I've tried different nightly builds (bitwise =]) to see when the bug was introduced.
By the way, http://www.heidisql.com/download.php is a really handy page for this
purpose, and it helps a lot that you can just click and run an old HeidiSQL version.
The last version that worked OK was nightly build 1587.
The bug was introduced in the next build (1590).
Build 1588 and 1589 are not available for download, but these are the comments in
SVN for them:
[1588]
* Set Zeos 'Writable' and 'ColumnName' properties to make the result set metadata
usable for creating update statements.
[1589]
* Avoid database metadata calls if the appropriate column information is already
available. Fixes issue #315.
[1590]
Bugfix: compare Unicode streams when scanning for updated data to post. Fixes [issue
569](#569) (hopefully).
Hope this helps.
Related
Tickets:
#315View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Please starr issue 618 (click the white star so it gets yellow) to be notified on
relevant updates.
Related
Tickets:
#618View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: SuperNiFF@gmail.com
This issue seems to be fixed with the latest versions that use the TVirtualTreeView
component.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
(No comment was entered for this change.)
Status: Fixed