Generally statements like this are non-sensical. There are hundreds of
Verity based applications out there performing very nicely thankyou.
You can't just write-off an application like Verity on account of having
a slow solution -- more than likely it is your solution implementation
that is buggered, and not the Verity engine.
That's not to say Verity is the be all and end-all but the solution does
work and it is read-optimised to be very fast.
-- geoff
http://www.daemon.com.au/
Andy Ousterhout wrote:
> Yikes. Guess I'll need to go back to the SQL search I had designed. Wasn't
> as pretty, but a whole lot faster.
>
> Thanks.
> -----Original Message-----
> From: Barney Boisvert [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 01, 2003 8:09 PM
> To: CF-Talk
> Subject: RE: Update Verity Collections Execution Time
>
> Yeah. Verity is slow. We had a collection (designed by a developer
> before
> my time, I might add) with about 10,000 items in it. Inserting a new row
> took upwards of 45 seconds on a reasonably beefy machine (dual P-III 666).
> As you might imagine, that quickly got scrapped in favor of the very
> speedy
> FULLTEXT search from MySQL.
>
> Cheers,
> barneyb
>
> > -----Original Message-----
> > From: Andy Ousterhout [mailto:[EMAIL PROTECTED]
> > Sent: Monday, December 01, 2003 6:02 PM
> > To: CF-Talk
> > Subject: Update Verity Collections Execution Time
> >
> > Does it sound correct that adding a single record to a verity
> > collection thru
> > action = ''My Goodness Cookies
> > www.omygoodness.com
> <http://www.houseoffusion.com/banners/view.cfm?bannerid=17>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
