I have a table that looks like the following
<SQL "CREATE TABLE tForms (FormID int, FormType int, TextBlob varchar(256))"></SQL>
and I create an index on it like so:
<SQL "CREATE METAMORPH INVERTED INDEX IXT_tForms on tForms (TextBlob, FormID, FormType)"></SQL>
When I do a likep search on TextBlob a linear search happens as evidenced by the fact that hits occur on substrings, i.e. a search on "bar" will hit on "foobarquack". This will be too slow for large data sets. Is there something wrong with the creation of my index? "allinear" has been left at its default value of 0.
My texis version is
Commercial Version 3.01.992447526 of Jun 13, 2001 (i686-intel-winnt-32)
After data has been inserted into tForms you will need to update the index. This should happen automatically with chkind when sufficient data has changed, or you can reissue the CREATE INDEX without a DROP INDEX to force a manual update.
The query I am doing was from the TSQL command prompt:
SQL 1>select * from tForms where TextBlob likep 'bar';
I made no modifications to apicp settings before doing this query, so I assume everything is set to default values.
Regarding index updating, this query was done following the new creation of the metamorph index.
And bar does not occur in that TextBlob as a standalone word? Records added after the creation of the index might be found, and depending on how you do highlighting substrings may show up.
Vortex will not even linear search without the index with the default allinear setting.
Is it possible that records found after the creation of the index might be linearly searched even though the rest of the table is not? My concern was that the entire table was being linearly searched which would be extremely slow in a live situation.
