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 151634 - SQL History: Order of statements is by ascending date when using matchbox
Summary: SQL History: Order of statements is by ascending date when using matchbox
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: John Baker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-28 18:30 UTC by John Baker
Modified: 2009-04-28 03:23 UTC (History)
2 users (show)

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 John Baker 2008-10-28 18:30:58 UTC 
- Create Sakila
- Run some queries against actor table
- Bring up history
- filter with string 'actor'
- Should show the latest statements first by default, right?  But the oldest statements show up first.
- Click on date column - the latest statements still don't show up first
- Click on date column - now they show up
Comment 1 John Baker 2008-10-29 21:53:34 UTC 
e31b08d1d13b
Comment 2 Quality Engineering 2008-10-30 04:58:25 UTC 
Integrated into 'main-golden', will be available in build *200810300201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/e31b08d1d13b
User: John Baker <jbaker@netbeans.org>
Log: #151634 fixed
Comment 3 Roman Mostyka 2008-10-30 18:09:52 UTC 
Verified with build 081030.
Comment 4 pgebauer 2008-11-10 15:10:15 UTC 
Since this issue is P3 priority, in accord with rules "How to include issues into patch"
(http://wiki.netbeans.org/NetBeansPatches) it must include an explanation as to why its backport is necessary and how
safe it is.

Could you please provide such explanation?
Comment 5 Roman Mostyka 2008-11-10 17:51:47 UTC 
John, could you include an explanation as to why its backport is necessary?
I don't think that order mode is very painful for customers, at least because they can easily change it since you've
implemented this feature in "SQL History" dialog.
And could you tell also how the fix is safe if you still think that this fix should be in the Patch 1?
Comment 6 John Baker 2008-11-10 18:10:25 UTC 
Backport is not necessary.  Fix results in consistent behavior and is nice to have
Fix is relatively safe
Comment 7 Michel Graciano 2009-04-28 03:23:00 UTC 
Be careful with it since this patch has an regression. See issue #163805 for details and patch. Comments are welcome.

Regards