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

[Da-fan.Yang@xxxxxxxxxx]

Hi,

When designing and implementing this
part, we assume that the input is string, that is what I call "raw
data" ( not row data). Since the "raw data" is defined as
a literal string, it must be a limitation for the consumer. Without this
assumption, we can not implement the import/export capabilities of Execution
Plan View.

As to the tree-structure graphic plan
part, currently we depend on draw2d. It will be better to use GEF, but
that needs time and resource, I suppose we will swtich to GEF in the future,
but thanks so much for your good suggestion.


Best Regards & Wishes

Idull

Sybase China.
S/W Eng - Dev
Tel:0086-021-68799918-3102

Vasantha Jayakumar <vasantha@xxxxxxxxxx>

09/26/2006 04:41 AM

To	Da-fan.Yang@xxxxxxxxxx, jograham@xxxxxxxxxx
cc	dtp-dev@xxxxxxxxxxx
Subject	SQL Execution Plan ...

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