Invalid data selection when index is turned on (AREV Specific)
At 05 AUG 2002 04:07:30PM Leon Shaffer wrote:
Configuration
Server running Novell 4.11 with RTI NLM 1.5aWorkstations running W98SEAREV v3.12Problem
In Item Master table, when I create a BTREE index on a true data field (SIZE), then do aSELECT ITEM_MASTER WITH][size=7'
the selection returns 67 rows
but with index removed from the size field and doing the same selection, I get the actual # of records returned of
128
I have removed the index and then re-installed the index, but
to no avail.
The data is valid, and there are no GFE's, nor have there been any
GFE's.
There was some "bad" data in the ITEM_MASTER table, so I backed up
the table (twice - you can never have enough backups), cleared the
table, and wrote all rows from the backup table back into the ITEM__MASTER tableā¦.this did not get rid of the "bad" data, so I
deleted the ITEM_MASTER table (after removing ALL indexes), re-created the table called ITEM_MASTER, copied all "good" data back into the new ITEM_MASTER table, verified the data, re-created the
indexes, and though I was a happy camper until the selection problem arose!!!
Any help is appreciated!!!
At 05 AUG 2002 04:22PM Jonathan Bird wrote:
1. Ensure you have no demlimiter marks in any keys in the table
2. Ensure the length of the indexed field is greater than the longest data in the field in any row.
3. Is the justification correct?
J
At 05 AUG 2002 04:28PM Leon Shaffer wrote:
The delimiters was the "bad" data that I had to remove. That was why I had to delete the table and write a program to copy all the rows back into the newly-recreated ITEM_MASTER table.
I will re-check the length
Thanks for the response
At 05 AUG 2002 04:47PM leonshaf wrote:
I have checked the keys in the data table, and there are no
delimiters in any of the keys. Total number of records in
the table is 1,216 - so a fairly small table. I have verified that the number of characters to show for the SIZE column is set so as to make sure that it is wide enough for the maximum entry in the column.
I have again created the index for the size column, did a select, and it still did not return the correct # of records (keys).
At 05 AUG 2002 04:59PM Oystein Reigem wrote:
Leon,
What if SIZE is a VOC thing that means the length of the record? Does it help to change the name of the field to something else?
- Oystein -
At 06 AUG 2002 12:59PM Richard Hunt wrote:
I am not a knowledgeable BTREE index user or expert. I do think that just maybe, maybe the "conversion", "justification" and "length" of the dictionary item "SIZE" might effect the indexing.
Maybe, just maybe if the conversion of "SIZE" is "MD0,", so that the output display of 7000 would be 7,000; just maybe that would effect the indexing???
Does the indexing work the same if the dictionary item's justification is "L"eft, "R"ight, or "T"ext?