Editing grid - cancel changes bug

[goran.genter]

When I change some value in grid, and then click F5 button (without clicking on End Edit button below in grid) dbForge Studio displays the message box :

You have unsaved data changes. Would you like to apply those changes now?
Yes/No/Cancel

When I click on No, everything is ok. Changes are discarded.
When I click Cancel, unexpected thing happens. All changes are immediately commited to database. In fact, Cancel is doing everything just as Yes button, while it should do exactly nothing but to close the message box window

I don't think this works properly.

[alexa]

We will fix this issue in one of the next product builds and will notify you once it's available for downloading.

[goran.genter]

Altough most bugs were fixed in 4.0 version of dbForge Studio for SQL Server, this one is still not fixed. In my oppinion this is very dangerous one because you can corrupt your database without even knowing about it.

Pressing cancel on grid refresh still commits all edits to the database. It works ok in Cached Updates Mode, but when this mode is turned off it's not ok.

[alexa]

A closer look at this revealed that following behavior is by design. This means that when navigating to the next row, the data get committed automatically. When clicking 'Cancel', only the last record doesn't get committed.

If you are observing a different behavior, please describe the steps to reproduce it in details.

You can send a reply straight to our support system at supportATdevartDOTcom

[goran.genter]

This is not the issue I was talking about.
I'm talking about this:

1. you edit some value (in normal edit mode - not cached), but you don't press the check button to commit values.
2. you press F5 to refresh the grid/query.
3. Message box shows asking you to apply the changes, "Yes"/"No"/"Cancel"
4. you press Cancel and changes to that cell/row are anyway commited to DB.

Correct behaviour should be that "Cancel" only closes the message box, and does not change anything else.

Now, it does something which is not expected.

"No" button however works as expected, and discards changes.

[alexa]

Thank you for the explanation.

We will fix it in one of the next product builds.