I would have to chime in here and state that Verity is broken in V7.
Here's why:
I upgraded from v6.1 Std to v7 Std this past weekend. In v6.1 all searching
worked perfectly for 2+ years. I use collections built from SQL queries
obtained from MS-Access (I know, I know - don't bash me for using Access,
it's a client decision).
As an example, a search on a small 270 recordset containing an ID, question
and answer is done on the word "Fact". Up pops 15 records. Good. However,
a search is performed on "Factoid" - no results. In 6.1 both search terms
would return results, in 7.0 only the word "Fact" returns results. The data
was entered by the client in January 2005, so we know it was working for
several months.
Problem solving on my end:
1) deleting and recreating the collections in the Cfadmin area, and
reindexing the collections - no resolution.
2) Installing the CFMX7 hotfix 2, which addresses some verity problems.
Restart CFMX7, delete and recreate collections from CFAdmin console,
reindexing the collections - no resolution.
3) Deleting the actual record from the db, then reinserting the record as
new, then reindexing - no resolution.
FYI - prior to reindexing, the Access db is compacted to make sure there are
no errors.
Here's the actual question text for this record:
Fact or Factoid - the addition of copper pennies to vase water increases the
life of tulips?
What's really weird is that this phrase will not even show up in the search
for "fact". Hmm, does the non-Unicode of this MS-access db have an effect?
Here's the code I use for indexing and searching (I have made no changes to
this code in 2+ years of use):
<!---Index the contents of the query object using CFINDEX--->
<cflock name="cfindexFAQ_lock" type="EXCLUSIVE" TIMEOUT="30">
<CFINDEX ACTION="REFRESH"
COLLECTION="faq_db"
KEY="faq_ID"
TYPE="CUSTOM"
TITLE="question"
QUERY="indexdb"
BODY="question,answer"
LANGUAGE="English">
</cflock>
<cfsearch collection="faq_db" NAME="v_faq" TYPE="SIMPLE"
CRITERIA="#FORM.criteria#">
Anyone else having these problems? Is this a bug, or are there code changes
in the cfindex routine that I need to tweak from 6.1 to 7.0?
If this can't be fixed, is there a way to run 6.1 Verity again, disable 7.0
verity, but keep 7.0 as the primary application server?
Thanks,
Mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211304
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
