Re: SQL source

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Really, I shouldn't have expected it given the description of the field 
is "SQL view create statement".  So this isn't an argument, just an 
observation for anyone else who might be thinking the way I was (rightly 
or wrongly).

On 8/12/2020 8:06 AM, Vernon Hamberg wrote:
> Hi Joe
>
> I don't see an inconsistency - a VIEW encapsulates a SELECT statement 
> that is run each time the VIEW is used, an INDEX has no statement to 
> encapsulate. Originally an INDEX was defined only by the key columns, 
> returning all columns. Now it is possible to define the returned 
> columns and put selectivity on it. I think, IIRC, that the key 
> "column" can be an expression, but I've not checked on that.
>
> So I see them as functionally different - a VIEW doesn't have an 
> access path defined, exactly - again, IIRC. the access path is set up 
> as the view is run. Optimization is handled as always, so the cache 
> might have what is needed.
>
> Cheers
> Vern