Is there a limit to the number of hits you can have returned from a @0 intersection search?
For instance, someone ran a search like so:
"select * from mytable where myfield like 'AA3 ZX4 <snip> @0"
...where the <snip> represents 248 additional search terms.
When we run the search, exactly 100 hits are returned, even though each of the 250 terms is in the table. Since 100 sounds like too round a number for coincidence, we were wondering if there's a limit we've bumped up against? Thanks.
It's not a hit limit. It's a query limit. You should have seen a warning message in the source of the results page and/or vortex.log. You're limited to 100 terms/sets per like/likep statement. Each parenthetical equiv set is limited to 200 terms. So you could have up to 20,000 words in a single like/likep query.
Sorry-- kinda lost me there at the end; "parenthetical equiv set"?
Does that mean what I think, in that you can fit 100 terms into a like statement, and using OR connectors for instance, tie the "like"s together, to the tune of 20,000 chars total query size?
I'm talking about all in one like or likep clause.
A set may be a single term, "term1", a phrase "term two", a wildcard "term3*", a parenthetical list of words "(word1,word2,word3)" (up to 200 words per list), etc. up to 100 sets per like/likep.
... like 'term1 term2 (eqterm1,eqterm2,...,eqterm200) term4 term5 (eqterm1,eqterm2,...,eqterm200) term6'
Note that the words within an equiv set are only words or phrases. Wildcards, rex, etc. are not allowed in an equiv list. Also, do not use any extra spaces within an equiv set.
