Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354057 - SQL result set viewer cannot display all table columns when table has 630 columns
Summary: SQL result set viewer cannot display all table columns when table has 630 col...
Status: CLOSED DUPLICATE of bug 318655
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-05 16:45 EDT by Chunqiu Ji CLA
Modified: 2011-10-03 10:28 EDT (History)
2 users (show)

See Also:

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 Chunqiu Ji CLA 2011-08-05 16:45:03 EDT 
1. The database object table has 630 columns.
2. Run SQL: SELECT * FROM table-name;
3. View the SQL result set in SQL result view, and see only the first more than 300 but less than 400 columns are displayed in the SQL result view.

Expect to see all 630 columns are displayed in the SQL result view.
Comment 1 Felipe Heidrich CLA 2011-08-08 11:31:12 EDT 

*** This bug has been marked as a duplicate of bug 318655 ***
Comment 2 Chunqiu Ji CLA 2011-09-30 14:42:51 EDT 
Hi Eclipse open source team,
Can you help answering the following two questions the customer who encountered this bugzilla problem asked:

1. What is the limit value of the total characters can be shown horizontally in the table viewer?

2. What is the plan / schedule to get the problem addressed by Eclipse / Microsoft team?

Thanks!
Comment 3 Felipe Heidrich CLA 2011-10-03 10:28:37 EDT 
(In reply to comment #2)
> 1. What is the limit value of the total characters can be shown horizontally in
> the table viewer?

It is not a character limit but a pixel limit. From what I remember a window can not be bigger than 0x7FFF pixels.

> 2. What is the plan / schedule to get the problem addressed by Eclipse /
> Microsoft team?

No plan, this is something that needs to addressed by Microsoft, I don't think they will fix that.

Sorry.