This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 136964 - Failed update of result set in ShowData is still displayed in results
Summary: Failed update of result set in ShowData is still displayed in results
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 6.x
Hardware: Macintosh All
: P2 blocker (vote)
Assignee: _ ahimanikya
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-11 01:08 UTC by David Vancouvering
Modified: 2008-06-26 18:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot of not reverted value. (109.81 KB, image/jpeg)
2008-06-26 13:02 UTC, Roman Mostyka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Vancouvering 2008-06-11 01:08:37 UTC
* Use Java DB travel database
* Select * from person
* Edit an entry in the id column
* Try to save the changes - you get an error dialog
* Close the dialog, the updated value is still there, when it should be reverted back to the original value.
Comment 2 Roman Mostyka 2008-06-26 13:01:13 UTC
I'm still able to reproduce this issue with latest sources (build 080625).
I see error message at the status bar, but wrong value isn't reverted back to the original value and it is still green.
Comment 3 Roman Mostyka 2008-06-26 13:02:08 UTC
Created attachment 63511 [details]
Screenshot of not reverted value.
Comment 4 _ ahimanikya 2008-06-26 18:49:23 UTC
This is by design.

Here is my reasoning: User makes couple of changes in a result page and now when commit it was not committed, since
there were some issue. 1st, he may not want to loose all the changes that he made so far just because there is a typo in
one of the column or row; 2nd, there is a cancel edit when pressed it will clear out all the changes; 3rd, for long run
query we will be running the query and user may have to wait for few seconds instead they could just clear if that is
the intent. So now user has more control and freedom. So I feel what we have is a feature by itself, so there is no need
to enhance this any further :)

If you still think we should do this, reopen and I will force a refresh after commit failed.