Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349433 - Data Source Explorer throws NullPointer while expanding Tables Node on some of the DBs
Summary: Data Source Explorer throws NullPointer while expanding Tables Node on some o...
Status: NEW
Alias: None
Product: Data Tools
Classification: Tools
Component: Data Source Explorer (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: dtp.connectivity-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-15 09:28 EDT by Missing name CLA
Modified: 2011-06-15 09:53 EDT (History)
0 users

See Also:


Attachments
Eclipse Error Message box (37.66 KB, image/pjpeg)
2011-06-15 09:35 EDT, Missing name CLA
no flags Details
stack trace (4.25 KB, application/octet-stream)
2011-06-15 09:36 EDT, Missing name CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2011-06-15 09:28:07 EDT
Build Identifier: 20110218-0911

Driver Sybase ASE 15
Connection properties set without Dadabase Name to show all databases on this Server.
This works fine for most of the DBs on this server, but when exploring some of the DBs by expanding Tables Node - it throws an Nullpointer
Maybe there are some characters which are not compatible or missing information on the tables.

Reproducible: Always

Steps to Reproduce:
1. Connect DataSource Explorer to a Sybase ASE 15 Server with multiple DBs
2. Explore DB by expanding the Tables node
3. on some of the DB's it throws an error, its always on the same DB's, others run fine. (I guess that there are some naming conventions or missing info)
Comment 1 Missing name CLA 2011-06-15 09:35:40 EDT
Created attachment 198019 [details]
Eclipse Error Message box
Comment 2 Missing name CLA 2011-06-15 09:36:12 EDT
Created attachment 198020 [details]
stack trace
Comment 3 Missing name CLA 2011-06-15 09:53:40 EDT
Note: the "same" DB Table node can be expanded on a different Testserver. So i guess it failes because of some data retrieved from the server. Probably "missing/expected" data (i.e owner, description) on your first Testserver.