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.
1. Execute bunch of statements against different connections. 2. Open "SQL History" dialog and order by statements. 3. Change connection in "Connections" drop down list. Result: Statements aren't ordered.
Slightly nice to have but this is not really inconvenient for the user - just click the table header to reset the order
Yes, workaround exists, but feature works improperly and it can make bad impression of IDE. And actually it isn't very convenient to change order every time after changing connection. If user tries to find something with 10 connections it can be very annoying. And main reason why this is P3: the feature should work properly. John, can you ask somebody else about their opinion?
I think you're missing something here. Selecting a connection will only show those statements executed for that connection (statements that are not executed by this connection will not be listed.) By changing the connection again to another connection then again only corresponding statements are listed. Here's one scenario: 1) Select a connection Result - statements removed 2) Set the ordering (by statement) 3) Select a different connection Result - different statements removed and new statements listed You expect the order to be retained by statement even after changing the connection and new statements appear ?
Yes, I expected exactly this. Is it wrong behavior or was it planned different?
By design, the connection dropdown resets the statements back to the default order setting
Please vote if you want to see this behavior enhanced. I'll send a message to the db alias also.
First of all, I don't think it is common for a user to have say 10 connections open. Most users are working with only one connection, and are not hopping about between connections. I can see this being a common QE scenario, but not a common user scenario :) I also see John's point that when you change connections, you get a new set of statements, so going to default ordering sounds acceptable to me. According to http://wiki.netbeans.org/BugPriorityGuidelines, a P3 means it is a "highly visible usability problem." A P4 is a "minor usability problem." I believe this is a minor problem, and I am re-prioritizing this to a P4. Thanks, David
No plans to fix in 7.0
Reassigned to new owner.
Current behaviour (main-golden) shows the behaviour the orginal reporter asked for. The sort order is constant even if connection is changed.