Force an index retrieval

[Robert J.M. Edis]

G'day Paul

I suspect that the 'for missing' syntax will cause a full table scan as the
process needs to find "the last non-empty occurrence of an item".  Even if
it is using the index, the whole index would be scanned.

I'm not a database expert but I believe most RDBMS's will trieve the data
based on its optimiser irrespective of whether you specify an index or not.
Specifying the index should ensure record retrieval in index order though.

Regards,

Blue

-----Original Message-----
From: Paul Howard
To: powerh-l@lists.swau.edu
Sent: 3/16/00 10:06 AM
Subject: Force an index retrieval

Hi Listers,
One of my customers is using PH 733d3 on hpux accessing a sybase
database.

Here is a sample of the code

> procedure FIND
> ;-----------------
> begin
>   for missing CUSTOMERS
>     begin
>       get CUSTOMERS &
>           viaindex idx02 &
>       using &
>           T_DEBTORS_MONTH, &
>           T_SURNAME
>     end
> end 

He finds that this does a sequential table scan instead of using an
indexed
read.  In ISQL you can force it to use an index with special syntax.
Does
anyone know how to do this from within PowerHouse?

Regards
Paul Howard
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= =
Subscribe: "subscribe powerh-l" in message body to
majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to
majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.