Btree.Extract limitation on OI 8.08 (OpenInsight 32-Bit)
At 24 SEP 2009 05:46:02PM Jim Leong wrote:
Is there a limitation on Btree.Extract as to how many keys it can return? I wasn't expecting to see any limitation on OI 8.08, but my reports were not right. So I decided to run a "Select" search on TCL and compare it to my Btree.Extract keys. When I ran a Btree.Extract I returned 309012 keys. When I ran a TCL search I got 390639 keys.
At 25 SEP 2009 08:48AM Richard Bright wrote:
Jim,
While we await the response to the substantive question, you might like to check in the Table Dict the display field length of the value being indexed . I believe you need a length 2 char greater than the max length of string else the values being indexed indexed are effectively truncated - leading to missed key returns.
At 25 SEP 2009 01:32PM Sean FitzSimons wrote:
Jim,
There isn't a limitation? I wonder… if you rebuild the index are the results different?
Sean
At 25 SEP 2009 01:34PM Sean FitzSimons wrote:
My fingers, not my brain, was doing the work.
There isn't a limitation?
should be
There isn't a limitation.
Thanks,
Sean
At 25 SEP 2009 02:09PM Jim Leong wrote:
Good to know there isn't a limitation.
I did increase the display length as Richard suggested, but it did not make a difference.
I will reindex the table and try it again.
Thanks
At 26 SEP 2009 08:34PM Barry Stevens wrote:
]]I did increase the display length as Richard suggested
The index will have to be REMOVED, then re added
At 27 SEP 2009 05:26AM Warren Auyong wrote:
If I recall correctly you can "cheat" and simply delete the ! record in the !file then logout or reattach the file and then rebuild the index.
At 01 OCT 2009 12:54PM Jim Leong wrote:
I done "all of the above" and have concluded there is a limitation of of keys returned from a Btree.Extract. The number of keys is roughly depending on the length of the keys. In one instance, the btree.extract should have returned 1,880,354 keys but only 352,888 were returned.