Homo-Adminus Blog - Latest Comments in Innodb Locks, ActiveRecord and acts_as_ferret Problem

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Scoundrel — Wed, 12 Dec 2007 09:12:47 -0000

2Michael: I've never filled it as a bug, cause' I wasn't sure that it is a bug. Feel free to file it in rails trac if you think it is.

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Michael Klishin — Tue, 11 Dec 2007 21:12:27 -0000

Nice. Has it been filed to Rails Trac? I'm actually digging AR sources and trying to help core team with fixes. So should I create ticket for this first or can you please point me to it?

There's about 10 000 tickets in their Trac :(

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Khaled Hassounah — Mon, 03 Dec 2007 03:54:24 -0000

check out solr and acts_as_solr...

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Scoundrel — Sun, 02 Dec 2007 15:46:36 -0000

At this point we've just decided to stick to the technology we've used to. I mean both customer and me use sphinx in many places and sphinx integration process looks much easier for us at this moment.

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Frank Mashraqi — Sun, 02 Dec 2007 10:22:41 -0000

I understand. Have you evaluated Lucene as an option?

Frank

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Scoundrel — Sat, 01 Dec 2007 16:25:40 -0000

Frank,

AFAIU, they simply did not hear about nginx back then and started using what everyone else in Rails community was using - ferret. Later many people I know migrated away from ferret, but when our client was creating his service, ferret was one of the most popular SE solutions which have Ruby client libraries and/or Rails plugins.

Re: Innodb Locks, ActiveRecord and acts_as_ferret Problem

Frank Mashraqi — Sat, 01 Dec 2007 12:58:52 -0000

Question: Why is your client with "largest site" using acts_as_ferret in the first place?