Re: [dtp-dev] SQL Execution Plan ...

[Anil T Samuel <anil.samuel@xxxxxxxxxx>]

Hi

I am working with Exec. plan feature to extend it for Oracle plugin.

1. How wud the TreeEditPart benefit compared to TreePlanDrawer that is 
current.
2. My suggestion is to encapsulate the common plan details into a class 
and use same to draw the basic tree view and let DTP consumers extend 
the class and view models for their purpose.
3. raw data in XML format and a HTML table renderer (for view) for same 
wud be ideal.

Regards
Anthos

Vasantha Jayakumar wrote:

> Hi
>
> I reviewed the draft design plan for the SQL Execution Plan and I have 
> a couple of questions regarding this.
>
> 1. For the "Tree-structure graphic execution plan", I was wondering if 
> we could instead use GEF here and use the TreeEditPart to define the 
> tree structure?
>
> 2. The input to the SQL Execution Plan mentioned in the draft is "row 
> data" which refers to the actual catalog rows. How would we go about 
> standarizing the format of this input? For example, would we specify 
> the minimum set of data fields to be included in the row data? If so, 
> we would need to include this in the design.
>
> 3. For the input format to the SQL Execution plan, does anyone have 
> requirements to use different types of input other than row data?
>
> I appreciate your help with this.
>
> Thanks,
> -Vasantha
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dtp-dev mailing list
> dtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dtp-dev
>