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 137612 - SQL History: Empty row is shown for not matched statement
Summary: SQL History: Empty row is shown for not matched statement
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: John Baker
URL:
Keywords:
: 137783 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-18 17:54 UTC by Roman Mostyka
Modified: 2008-08-05 13:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screenshot of empty row without borders. (25.81 KB, image/jpeg)
2008-08-04 19:14 UTC, Roman Mostyka 		Details
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-18 17:54:20 UTC 
1. Open SQL editor.
2. Execute statement.
3. Execute another statement.
4. Open SQL History dialog. "SQL Executed" table contains 2 rows.
5. Write something, that match only one statement, in "Matching SQL" field.

Result: Only one record is shown, but instead of second empty row is shown. There should be only one row.
Comment 1 John Baker 2008-06-18 18:55:16 UTC 
I see - the size of the result is not updated
Comment 2 John Baker 2008-06-20 09:41:18 UTC 
cosmetic
Comment 3 John Baker 2008-06-20 09:46:25 UTC 
*** Issue 137783 has been marked as a duplicate of this issue. ***
Comment 4 John Baker 2008-08-04 03:04:56 UTC 
c4cf6d4e7a9f
Comment 5 Quality Engineering 2008-08-04 15:40:36 UTC 
Integrated into 'main-golden', available in build *200808041401* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/c4cf6d4e7a9f
User: John Baker <jbaker@netbeans.org>
Log: #137612 SQL History: Empty row is shown for not matched statement
Comment 6 Roman Mostyka 2008-08-04 19:11:06 UTC 
I still see empty row without borders. And I see changes from the changeset in my sources.
Comment 7 Roman Mostyka 2008-08-04 19:14:05 UTC 
Created attachment 66520 [details]
Screenshot of empty row without borders.
Comment 8 John Baker 2008-08-04 19:23:07 UTC 
I can no longer reproduce after my fix using the steps in this issue and other steps both executing statements from the
same connection or different connection.

Need new steps.  If they are the same steps then you need to make sure again your build has the changeset
Comment 9 John Baker 2008-08-04 19:29:50 UTC 
Fix made it in the beta branch;  better to test use beta instead anyways
Comment 10 John Baker 2008-08-04 20:24:44 UTC 
From the screenshot, it doesn't appear to be an empty row, but some painting problem.

If you click on the table does the white space get cleared up?

If this is a painting issue then this would be a different bug.
Comment 11 John Baker 2008-08-04 21:55:38 UTC 
On Mac, I don't see the blank white line (probably because the background colors of cells is white), but on Windows I
see it.

However this is a different issue and it's been there for awhile.
Another way to reproduce is to do the following (at least on Windows, not doesn't appear on Mac):

1) Execute SQL from multiple connections
2) Open SQL History and choose a connection

Note the extra white space

A different issue should be filed.
Comment 12 Roman Mostyka 2008-08-05 13:13:26 UTC 
Verified with build 080805.