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 119299 - Association of tables cannot be specified in the graph
Summary: Association of tables cannot be specified in the graph
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: John Baker
Depends on:
Reported: 2007-10-18 02:33 UTC by John Baker
Modified: 2009-05-25 21:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description John Baker 2007-10-18 02:33:34 UTC
In previous releases, a join operation could be created using the Graph section by dragging a column from one
table to another table

This doesn't work in 6.0
Comment 1 John Baker 2007-10-18 02:34:46 UTC
May have to waive this for 6.0

workaround is to use the SQL editor pane to create the join using SQL statements
Comment 2 John Baker 2007-10-19 03:02:03 UTC
workaround, edit sql statement by adding a join operation.
Comment 3 John Baker 2007-10-23 10:08:32 UTC
> You can do joins based on existing foreign keys. But it seems you can't do ad-hoc joins (joins of tables that have
logical relationships, but not foreign keys for them -- common on MySQL I think). This might be a P2, especially 
considering that we will want to attract PHP people (which very often use MySQL) to 6.0.

Joins based on foreign keys are created on-the-fly when adding a 2nd table.   However, if the link that connects 2 graph
nodes representing the join  is removed then
the link cannot be restored by click-drag-release (from one graph node to the other).
I agree this one should remain a P2
Comment 4 John Baker 2007-10-25 03:00:57 UTC
The issue isn't that there's a bug in connecting nodes, it's just that this feature wasn't implemented.

It looks like a the GraphScene needs a ConnectionProvider.  

I'm currently implementing but may be interrupted by other issue
Comment 5 John Baker 2007-10-25 07:49:01 UTC
Since a new class and public APIs will have to be introduced, I'm leery to start this if an API review is required.

I think it's too late for the review and we may have to live with this limitation of not being able to create joins by
connecting graph nodes.
Comment 6 Andrei Badea 2007-10-25 09:58:58 UTC
What is the new API needed for?
Comment 7 John Baker 2007-10-25 18:57:10 UTC
desc5: "GraphScene needs a ConnectionProvider"

ConnectionProvider is needed to support connecting nodes.

This is the feature that is missing - 

User clicks on a database column within a node and drags to another column in a node.
If columns can be joined then the connection is made
Comment 8 Pavel Buzek 2007-10-25 20:35:15 UTC
Given there is the workaround in adding joins in source and that it is not reported by actual users I think it is OK to
track this as a P3. Feel free to still work on the fix, it does not change anything in that sense.

I also do not need what new API needs to be introduced. It would seem that visual query editor needs to USE the
ConnectProvider, which is already a public API.
Comment 9 John Baker 2007-10-25 23:17:07 UTC
Correction, no new public API(s) required.

This isn't really a defect, the feature just wasn't implemented.   I marked as an enhancement but maybe feature is a
more appropriate Issue type.

Also there's more to do then implementing drag and drop because the implementation of GraphScene was done incorrectly.
It holds a hard reference to the old Graph library instead of using a Controller to provide the information to be
presented in the node.

I will downgrade since this is not a defect and there is a workaround to use the SQL text area to create queries. I can
still work on this but this is a lower priority and I cannot guarantee it can be implemented for 6.0

Comment 10 Jayashri Visvanathan 2007-10-25 23:59:25 UTC
Should probably be a defect considering that this was not taken care of when the graph library migration happen.
Comment 11 David Vancouvering 2008-01-17 01:24:24 UTC
I'll also be disabling these tests until this gets fixed.  I don't think they're important tests and they make it hard
to evaluate new bugs because of the failures.
Comment 12 David Vancouvering 2008-01-26 00:11:58 UTC
Sorry, that last comment was for the wrong bug :(
Comment 13 Petr Blaha 2008-11-18 13:15:44 UTC
Move visualsqleditor subcomponents below visualweb