The question is more to find a way to keep the information that subquery is called T.
This could be done by adding:
- a label/comment in the subquery graph,
- a new kink of edge/link between node/subgraph - node/subgraph (not field to field),
- the alias node in the subgraph perimeter (proposal transmitted directly to your e-email with a .dot exemple)
This could be difficult …
Regards
PAscal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
Select t.id from (select id from test) t;
Generates two nodes without edge.
Would it be possible to add one edge (of a new type) between the subquery node and its alias T ?
Regards
PAscal
The subselect is not correlated with the outer select. There is no table.field in (select) .
All that this does is to select again the fields from the subselect . Why joining the outer and inner id fields?
-Alex
Hmm, this is actually a bug
No, there isn't any bug here !!!
The question is more to find a way to keep the information that subquery is called T.
This could be done by adding:
- a label/comment in the subquery graph,
- a new kink of edge/link between node/subgraph - node/subgraph (not field to field),
- the alias node in the subgraph perimeter (proposal transmitted directly to your e-email with a .dot exemple)
This could be difficult …
Regards
PAscal
See v0.40 for subselects . In previous versions used to do same: add a dummy node in subselect and link to it.