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 137997 - SQL History: "SQL History" button is enabled even if no statement is saved
Summary: SQL History: "SQL History" button is enabled even if no statement is saved
Status: RESOLVED INVALID
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P4 blocker (vote)
Assignee: John Baker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-23 17:19 UTC by Roman Mostyka
Modified: 2008-08-11 19:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2008-06-23 17:19:01 UTC 
1) Start IDE. Open SQL Editor. "SQL History" button is disabled.
2) Execute statement. "SQL History" button becomes enabled.
3) Open "SQL History" dialog and save 0 last statements. Table will be cleared. Close "SQL History" dialog.

Result: "SQL History" button is still enabled, even there is no saved statements.
Comment 1 John Baker 2008-08-03 08:14:22 UTC 
won't fix.  Somewhat risky.
Comment 2 Roman Mostyka 2008-08-04 10:31:28 UTC 
Not for this release if the fix is risky, but issue is in NetBeans and we should fix it, probably for next release or
for NetBeans 6.5 patch.
Comment 3 John Baker 2008-08-04 11:55:45 UTC 
This is a very minor inconvenience.

Is this really a P3 ?  
A really good justification is needed
Comment 4 Roman Mostyka 2008-08-04 12:00:47 UTC 
One very minor inconvenience. But there are a lot of such very minor inconvenience and as result bad impression of IDE.
And I'm not sure that it is hard to fix.
John, if you think that it is P4, you can decrease priority, but I think that it is P3 at least because it should be
easy to fix.
Comment 5 John Baker 2008-08-04 19:39:54 UTC 
Not a P3.   User will rarely set the save limit to 0 and no effect on the functionality of the dialog. More of a
cosmetic issue
Comment 6 John Baker 2008-08-11 19:47:37 UTC 
If the user sets the save limit to 0, SQL History must be available to reset the value.  So, it doesn't make sense to
not disable the button otherwise SQL History cannot be opened.