do you have ANY where clause in your SQL query (that the verity builds
collection on)?
maybe maxrows?
try getting the query.recordcount before creating the index - see what it
shows.
I'm using CF 4.5 Verity for over 5,000 rows, it's not alot, but it's more
then you have
so it's YOUR problem, I gu
> do you have ANY where clause in your SQL query (that the verity builds
> collection on)?
> maybe maxrows?
>
> try getting the query.recordcount before creating the index - see what it
> shows.
> I'm using CF 4.5 Verity for over 5,000 rows, it's not alot, but it's more
> then you have so it's YOU
Disk Space?
Maybe Quota?
Try specifiying a diffrent path for the collection
Thanks,
Michael
- Original Message -
From: "Philip Arnold - ASP" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, June 14, 2001 1:25 PM
Subject: RE: Verity L
> Disk Space?
> Maybe Quota?
> Try specifiying a diffrent path for the collection
Here's how it's going now...
I transferred the collection from a drive which had 2Gb free to one which
had 27Gb free
The user that CF uses has Admin privelages (at the moment), so it's allowed
full access to all dr
it helps - start to look intresting.
Thanks,
Michael
- Original Message -
From: "Philip Arnold - ASP" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, June 14, 2001 2:35 PM
Subject: RE: Verity Limit
> > Disk Space?
> > Maybe Qu
try using a '%' instead of a '*'
-Original Message-
From: Michael Lugassy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 14, 2001 8:55 AM
To: CF-Talk
Subject: Re: Verity Limit
Try adding another colum with the value "justtestingveritystuff" in each
row,
> try using a '%' instead of a '*'
% does nothing for Verity on it's own - not sure what it does with other
characters...
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**
> Try adding another colum with the value "justtestingveritystuff" in each
> row,
> now re-index, with that colum in the body and/or title - now run a search
> for "justtestingveritystuff"
>
> maybe searching by "*" has it's limitation, god knows..
> let me know if it helps - start to look intrest
I'm thinking the key you are using isn't unique. Could you post the code
you are using to create the collection.
dave
At 10:50 AM 6/14/2001 +0100, you wrote:
>I'm having a problem with a Verity collection...
>
>I have one table build with 6,800 records, this isn't fantastically big, but
>the pr
What does your query look like? Have you run it 'straight' and outputted
the results of that query? Maybe you're not getting the results you think
you should be getting because it's something in your query.
Judith
Philip Arnold - ASP put into words:
> > Try adding another colum with the value
> I'm thinking the key you are using isn't unique. Could you post the code
> you are using to create the collection.
Below is the SQL used to build, add and select the database - then the
CFIndex command
The big table is meant to be built from about 230 mini-sites, each of which
having 15-20 pa
Philip,
Even trhough you can see 6,000+ records through the Enterprise Manager
doesn't necessarily mean that your SQL is successfully pully all 6,000+
records.
Try commenting out your CFINDEX and do a record count of all returned
'hits' from your database table.
This is something that I've h
What is the result if you do a SELECT COUNT (DISTINCT ID) FROM
[_Temp_Search_Table]?
If Verity sees duplicates for the key, it will fail on adding them to the
index.
dave
At 09:22 AM 6/15/2001 +0100, you wrote:
>> I'm thinking the key you are using isn't unique. Could you post the code
>> you
I've used Verity under 4.5x to index 60,000 odd records with no problems.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael
Lugassy
Sent: Thursday, 14 June, 2001 10:13 PM
To: CF-Talk
Subject: Re: Verity Limit
do you have ANY where clause in
14 matches
Mail list logo
