If I create a deleted() binary index for a dbf in xHarbour, do I need to set the filter to .not. deleted() if I already have the global setting of show deleted off?


asked 19 Sep '13, 11:43

Gary's gravatar image

accept rate: 0%

No, it should not be necessary to do that. The binary DELETED() index should get used automatically in appropriate situations. For example, if you set a filter such as:

field = 'somevalue'

then Advantage will change it to the following in the AOF engine (optimized filtering code):

field = 'somevalue' and .not. deleted()

With a binary index, it will also use it in other places such as GoTop() and Skip() in natural order. I don't remember the exact details but if Advantage skips over some number of deleted records it will load the binary index and use it to locate the next non-deleted record.


answered 19 Sep '13, 15:12

Mark%20Wilkins's gravatar image

Mark Wilkins
accept rate: 26%

Your answer to the original question.
If responding to a request for additional information, please edit the question or use the comment functionality.
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 19 Sep '13, 11:43

Seen: 1,288 times

Last updated: 19 Sep '13, 15:12

Advantage Developer Zone Contact Us Privacy Policy Copyright Info

Powered by Advantage Database Server and OSQA
Disclaimer: Opinions expressed here are those of the poster and do not necessarily reflect the views of the company.