Thanks, Arnon - I thought that was the case!
But I think it would be a very nice feature *IF* we could optionally specify that a index tag be created when a view has an ORDER. Something along the lines of a "... with INDEX" clause.
I think I'll add that to my "wish list".
Jim N
>>>Jim, when you include the ORDER clause in the SQL used to create the
>VIEW
>>>the subset will be ordered - no index will be created (just like regular
>>>cursors you know from the previous versions)
>>>and (again. like regular curors) you can create a temporary index on yjr
>>>subset you retrieved
>>>
>>Do you think this is a limitation on the use of views? For views with a
>>great number of records, there may be no quick way to order them (e.g.,
>for
>>clicking on grid column headers for reordering), as with preset table
>>indexes?
>>
>
>
>Bruce,
> the idea behind views is to save network traffic- by retrieving only the
>subset needed from the server
>big views kind of goes against that concept in the first place
>
>Arnon
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only