I've just being doing some tests of this and I must say I'm pretty impressed by the speed. Two things

1. Can we have a time taken indicator on the SQL page for the database - I'd prefer something better than me going 1 and 2 and 3

2. More importantly WITH DATA ignores any ORDER BY clause in the select statement. Is this what its meant to do? If so I need to create indices (oh the pain of no scripts and also change the way I handle changing sorting for the grid.

Roy Lambert

Roy,

<< 1. Can we have a time taken indicator on the SQL page for the database -
I'd prefer something better than me going 1 and 2 and 3 >>

If you're referring specifically to the CREATE TABLE AS, then yes, I'll see
what I can do.

<< 2. More importantly WITH DATA ignores any ORDER BY clause in the select
statement. Is this what its meant to do? >>

Sure, you're creating a table, and an ORDER BY doesn't really have any
bearing on this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<< 2. More importantly WITH DATA ignores any ORDER BY clause in the select
statement. Is this what its meant to do? >>>

<< Sure, you're creating a table, and an ORDER BY doesn't really have any
bearing on this. >>

I'm not sure if I agree with you on this one

One thing is that the ORDER BY clause isn't officially supported by the
<query expression> which is the basis of the CREATE TABLE AS construct.
However, as long as EDB support the ORDER BY clause as an extention to the
<query expression>, I think it should have the expected effect.

Ole Willy Tuv

Tim


><< 1. Can we have a time taken indicator on the SQL page for the database -
>I'd prefer something better than me going 1 and 2 and 3 >>
>
>If you're referring specifically to the CREATE TABLE AS, then yes, I'll see
>what I can do.

Basically I'd like to see the time taken for any sql statement of any of the pages in EDBMan. I appreciate that for a lot of operations the time taken will be a big fat 0, but on the other occasions it could be useful.

Roy Lambert

Tim


><< 2. More importantly WITH DATA ignores any ORDER BY clause in the select
>statement. Is this what its meant to do? >>
>
>Sure, you're creating a table, and an ORDER BY doesn't really have any
>bearing on this.

Which other keywords aren't supported eg DISTINCT, GROUP BY?

Roy Lambert

Ole,

<< I'm not sure if I agree with you on this one

One thing is that the ORDER BY clause isn't officially supported by the
<query expression> which is the basis of the CREATE TABLE AS construct.
However, as long as EDB support the ORDER BY clause as an extention to the
<query expression>, I think it should have the expected effect. >>

I understand.  I kept in the ORDER BY support because it does have one
"effect" - the index created for the ORDER BY can be used for optimizing
filters/queries on the created table.  It's just not visible at all.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< Which other keywords aren't supported eg DISTINCT, GROUP BY? >>

All of them are supported.  The only distinction is that indexes are used in
EDB for sorting query result sets, and the ORDER BY index simply isn't
visible in the created table.  Therefore, it can't be selected as the active
index, etc. when the table is later opened/viewed.

--
Tim Young
Elevate Software
www.elevatesoft.com