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 149863 - [65cat] SQL History UI should be right resizable
Summary: [65cat] SQL History UI should be right resizable
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: John Baker
URL:
Keywords:
Depends on:
Blocks: 152828
  Show dependency tree
 
Reported: 2008-10-11 14:08 UTC by Michel Graciano
Modified: 2008-11-18 12:33 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2008-10-11 14:08:44 UTC
[ BUILD # : 200810090201 ]
[ JDK VERSION : 1.6.0_07 ]

SQL History table should resize together with dialog.
Comment 1 John Baker 2008-10-11 23:07:21 UTC
Sorry, too late to fix for 6.5
Comment 2 John Baker 2008-10-12 07:33:49 UTC
You want to view the entire SQL, is that why you want to expand the width of the table or you do want to see more
rows?

Expanding the width doesn't necessarily allow the entire SQL to be visible since an SQL statment may expand to more than
one line.  To view the entire SQL, mouse over the SQL statement.

The SQL History really wasn't intended to be resizable, if it's too large then it covers up the SQL Editor so you can't
see where SQL would be inserted.
Comment 3 John Baker 2008-10-12 07:53:45 UTC
I suppose if you could resize the dialog so it's taller to see more SQL statements might be a nice feature.

If there are too many rows, you can limit the number by entering in some text in the Matching SQL textfield
Comment 4 Michel Graciano 2008-10-13 17:04:42 UTC
I just resize the window to see more data into the table, but it is not the question. Independently of my needs, when I
resize a window it should reorganize, in a better way, the components inside. This issue is no high priority but should
be fixed to improve the user experience.

Regards.
Comment 5 John Baker 2008-11-14 15:15:59 UTC
This just got fixed.

Sorry, I updated a duplicate issue.  

hmichel, you're welcome to add comments to 150663 if you want to see the fix integrated in the patch release
Comment 6 Roman Mostyka 2008-11-18 12:33:41 UTC
Verified with build 081117.