Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 10 JAN 2002 03:49:52PM Luis wrote:

Hello Group.

Somebody save for that when the function Betree.Extract is used with more that one search column, it is very slow???

On the other hand when it is used with a single search column (IndexedColumn) and with alone a value is very quick???

Any information is very grateful.


At 10 JAN 2002 07:13PM Richard Hunt wrote:

Luis,

I have experienced that happening with almost all indexing proceedures. The best way is to select using one indexed column. And then from that select result, continue the reduce (or selection criteria).

I also know that Btree indexes operate and react differently than do Crossreference indexes.

Very rough example…

Table: INVOICES

Indexed Column: DATE

not Indexed Column: AMOUNT

If you want to select all INVOICES with DATE equal to "12-31-01" and the AMOUNT greater than "100.00"…

SELECT INVOICES WITH DATE EQ "12-31-01" AND WITH AMOUNT GT "100.00"

 would probably be much slower than...

SELECT INVOICES WITH DATE EQ "12-31-01"

 then from that select result do the second select...

SELECT INVOICES WITH AMOUNT GT "100.00"


At 14 JAN 2002 01:01PM Luis B wrote:

Thank you Richard. Your information has been useful

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/6f58fe3d127c4cc588256b3d00726dce.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1