Tim,

<< Hopefully at some point in EDB's lifetime I will be able to add the
ability to "push" such WHERE expressions down into the view itself so as to
realize the benefits of having the WHERE clause limit the number of rows
being grouped. >>

That's actually the kind of optimization I would highly appreciate, not only
in views, but also in HAVING expressions where the filter can be applied
early in the query processing.

<< However, that is pretty complicated and won't be around for some time. >>

Well understood

Ole Willy Tuv

Hello,

> << Hopefully at some point in EDB's lifetime I will be able to add
> the ability to "push" such WHERE expressions down into the view
> itself so as to realize the benefits of having the WHERE clause limit
> the number of rows being grouped. >>
>
> That's actually the kind of optimization I would highly appreciate,
> not only in views, but also in HAVING expressions where the filter
> can be applied early in the query processing.
>
> << However, that is pretty complicated and won't be around for some
> time. >>
>
> Well understood
>
> Ole Willy Tuv

Oh come on!!! You (plural) don't entertain people in
this newsgroup any more ? It's getting boring!

I request the Ole vs Tim arguments back! <bg>

--
Charalabos Michael - [Creation Power] - http://www.creationpower.gr

Ole,

<< Well understood >>

Let me re-phrase that - the actual process is not particularly complicated.
The issue is that, for right now at least, the views are compiled once and
shared among all query cursors on the view in a given session.  Since each
query cursor may want a different WHERE clause pushed down on the view, it
makes the current architecture a little off.  That's the "difficult" part.


--
Tim Young
Elevate Software
www.elevatesoft.com

Michael,

<< I request the Ole vs Tim arguments back! <bg> >>

No way.  No more stress.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Mihail,

<< Oh come on!!! You (plural) don't entertain people in this newsgroup any
more ? It's getting boring! >>

Oh, sorry about that. I'll see what I can do

Regards,
Ole

Tim,

Ok. I'll go for the query then. Thanks for explaining.

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:3DADA730-D545-4421-BD0F-3C32AEF14DCF@news.elevatesoft.com...
> Harry,
>
> << It is a lot slower then executing a query with a where clause (I guess
> because the filtering is happening after the whole lot is grouped (like
the
> having). Do I understand correctly that in this case a use of  a view
isn't
> the wisest thing to do? >>
>
> Well, views are the same as any other query, so there's nothing inherently
> worse about them.  It just so happens, however, that in this case that the
> straight query with the WHERE clause is faster.   Hopefully at some point
in
> EDB's lifetime I will be able to add the ability to "push" such WHERE
> expressions down into the view itself so as to realize the benefits of
> having the WHERE clause limit the number of rows being grouped.  However,
> that is pretty complicated and won't be around for some time.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>