Bug 184541 - Remove Dependencies folder from DSE
Summary: Remove Dependencies folder from DSE
Status: RESOLVED WONTFIX
Alias: None
Product: Data Tools
Classification: Tools
Component: Data Source Explorer (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: future   Edit
Assignee: dtp.connectivity-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2007-04-27 20:12 EDT by Anil Samuel CLA
Modified: 2013-11-14 17:51 EST (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 Anil Samuel CLA 2007-04-27 20:12:04 EDT 
Build ID: 1.0

Steps To Reproduce:
1.Connect to a database.
2.Drill down the connection in DSE.
3.Dependencies folder is visible at all layers.

How can I selectively remove this folder.

More information:
Comment 1 Der Ping Chou CLA 2007-05-07 14:08:45 EDT 
I will asist DSE or connectivity project to add Derby examplary code to demonstrate how dependency can used to capture, for example a view is dependending on other view or database table.

Der Ping
Comment 2 Rob Cernich CLA 2007-05-15 11:18:40 EDT 
Hey Der Ping,

Can you please update the target milestone for this item (e.g. RC1, RC2, Ganymede, etc.)?

Thanks,
Rob
Comment 3 Brian Fitzpatrick CLA 2007-07-13 10:18:14 EDT 
Der Ping, do we want to come up with this example code for the 1.5 stream? (as well as the head stream of course)
Comment 4 John Graham CLA 2007-12-04 13:23:50 EST 
Would like this to be considered for DTP 1.6.
Comment 5 Brian Fitzpatrick CLA 2008-01-28 18:54:05 EST 
Der Ping, is this going to be able to be done in the Ganymede M5 or M6 timeframe?
Comment 6 Brian Fitzpatrick CLA 2008-03-25 13:23:23 EDT 
Der Ping, has this one been addressed for Ganymede?
Comment 7 Brian Fitzpatrick CLA 2008-05-23 12:09:27 EDT 
Setting to future
Comment 8 Brian Payton CLA 2013-11-14 17:51:26 EST 
We are closing this as WONTFIX due to lack of resource to work on it.  If someone feels strongly that the problem should be fixed, please reopen, preferably with a patch for the fix.