similar to: duplicate search results

Hello list, I wonder if someone has some tips on joining a ferret search with a database. I have a rails project using a postgresql backend and I would like to utilize the superb performance of ferret for fulltext searching. The problem is that I have to joined the result with the database as I have some user access rights to different documents to take into account. Does anyone have

Hi Does acts_as_ferret support a :group clause? For e.g any rails options like :select or :group etc? or is it that it supports only few of such options?Like it supports :include Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ferret-talk/attachments/20070731/a74fb666/attachment.html

Hello, First the specs: ruby 1.8.6, rails 1.2.3, ferret 0.11.4, mongrel 1.0.1, mongrel_cluster 0.2.1 And the model''s aaf config: # Ferret search engine acts_as_ferret({:fields => {:name => {:boost => 10}, :summary => {:boost => 2}, :body => {:boost => 1, :store => :no},

I have multiple models all with: acts_as_ferret :fields => [...] (models = profiles, blogs, comments ) When I restart the server and perform any crud operation on one of the above models, the index is created/updated. If I then go and perform any crud operation on ANOTHER model, ...the index from that first model is being updated. Any ideas? Can acts_as_ferret handle this? Thanks

Hi, I just upgraded from acts_as_ferret 0.2/Ferret 0.9.x to acts_as_ferret 0.3/ferret .10.9, and i''m getting a strange behavior: searches are returning far too many results, most of them superflous. i''ll paste in my code below, it''s pretty simple. i''m googling like mad, and going through both the source and the forums, and having trouble finding what could

Hi, I''m having some problems with acts_as_ferret and indexing. I''ve got a simple 5 column table, and a corresponding Ruby model. I loaded 9 rows directly into the table using mysql (for live it''ll be about .5mil rows) and configured a Rails search page along the exact same lines as ferret_demo. Unfortunately, search wouldn''t return any results; following

I''m trying to sort my search results by Date, in descending order. I''ve done quite a bit of reading through the forums here, and I''ve tried two different suggestions. This just returns results in the same order as a search without a sort: sort_fields = [] sort_fields << Ferret::Search::SortField.new("ferret_created_at",:reverse => :true)

Hello folks, I have four models, each with their own separate index. Models = Articles, Blogs, MusicTracks, and MediaFiles I have individual searches within each section of the site working just fine, but I want to have a gloabl search that searches across all of them at the same time and returns the results ordered by score. Here''s how far I am now... def search query =

I am getting this issue also... Does anyone know what this is? When will Acts as Ferret be available for v10? Thanks for your help in desperation! Caspar wrote: > Okay previous post related to me trying to fix this problem with an > upgrade to ferret 0.10.0 but acts as ferret is obviously not compatible > with this new version of ferret. > My app is about to go into production and

I''m having problems sorting on untokenized fields. I have one field that sorts fine, but there are others that seem to sort on a different field. Here''s the index description: acts_as_ferret :remote=>true,:fields=>{:name=>{:boost=>2},:name_for_sort=>{:index => :untokenized}, :city=>{:boost=>2}, :city_for_sort=>{:index=>:untokenized},

Hey all, I''ve been really happy with ferret thus far and all my search on my site is based on it. One of the recent challenges I ran into is changing some of my pagination within my site. Until now, I just used the tutorials out there that talk about how to get pagination working with acts_as_ferret. Recently, I decided to change my pagination to begin using the "Paginating

Hi, I''m using Rails/AAF with Ferret 0.10.11, and my index occasionally (every few weeks, roughly) becomes corrupted. If the index is busted, until I rebuild it our users are unable to save anything. I get errors like the one below, and the save rolls back. My question is, is there any way to catch the error, and continue with the save even if the model isn''t indexed? What

Hi all, Is there a way to have searches no use some indexed fields, when processing a query? context: I have a model Foo that holds some information in two languages : - text1_nl, text2_nl, text3_nl and - text1_en, text2_en, text3_en Some other fields are common to both languages and indexed as well - first_name, last_name Depending on the visitor language choice I need to exclude the

I am unable to find results for models when one or more of the terms are not being indexed. Lets suppose I index a User on the phrase "Ruby on Rails." If I then search using User.find_by_contents("Ruby on Rails") I get no results, since "or" is a common term and does not get indexed. Of course, User.find_by_contents("Ruby Rails") works just fine. I

I set up ferret and it''s running fine normally. Now I want to hook up the backgroundrb server. However whenever I try to do a search, I get this error: (druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:1075:in `method_missing'' (druby://localhost:9010) ./vendor/plugins/acts_as_ferret/lib/remote_index.rb:20:in `find_id_by_contents'' (druby://localhost:9010)

hi! after wondering why i can''t find alot of records i eventually found the problem in the sqlserver_adapters implementation of "add_limit_offset!". the problem is when using MSSQL with the sqlserver_adapter paging will only work when at least one column is defined in ":order". for example i was indexing a table with 2912 records, the generated sql for the batches

Hi, I just installed ferret for the first time and integrated it with my app. On my dev machine it''s fine but on my production server I get this when I call find_by_contents(): Processing LinksController#results (for 24.185.105.59 at 2007-03-28 05:28:36) [POST] Session ID: 3f2dc7c17147c0e52178ba697a119833 Parameters: {"commit"=>"Search",

Hi, I had ferret working wonderfully but i am regretting doing a gem update today. I had alot of trouble first installing it and was really happy to have it working. The upgrade was from 0.3.1 to 0.4.0. The problem is; in the rails console, >> @results = Book.find_by_contents("peter pan") => #<ActsAsFerret::SearchResults:0x487040c @total_hits=0, @results=[]> Its indexing

After switching to the DRb server, I am experiencing strange behavior when sorting on score. My app was working as expected before the switch. Both before and after the switch, my app sorts properly on other fields, such as date. For sorting on score, I am using the following option find_by_contents option: :sort => Ferret::Search::SortField::SCORE Before switching to DRb, this worked

Hi, I''m new to using ferret (and fairly new to ruby/rails) and I''m having a problem I can''t fathom. Sorry for the long post ... I have a test which passes require ''rubygems'' require ''ferret'' include Ferret require ''test/unit'' class CompanyTest < Test::Unit::TestCase def test_index puts ''running