similar to: FULLTEXT search in MySQL on rails

Hi, I have been using myisam tables in mysql with rails because my client will soon want fulltext searchable content, however when I migrated my development db from schema.rb all of the tables generated were innodb. I understand that I can override this, but also like the transactions and foreign keys of innodb. So 2 questions really: 1. are transactions in activerecord dependent on innodb or do

I''m wondering if ferret has any built-in search/replace mechanism that I might be able to use to highlight the query data in each search result. The reason I think this would be a good idea is that I could end up having to practically duplicate the ferret query parser just to interpret the query so that I can figure out how to highlight the keywords in the search results. Just in case

Along with the contents of the documents in my index, I have stored the date they were added. I want to search for keywords in the index but have the results be sorted by their date rather than their relevance to the keywords. How would I do this in ferret? Thanks, Carl

FYI, I tried installing ferret on my freebsd virtual server and got this: retango# gem install ferret --include-dependencies Attempting local installation of ''ferret'' Local gem file not found: ferret*.gem Attempting remote installation of ''ferret'' Updating Gem source index for: http://gems.rubyforge.org Building native extensions. This could take a while...

Hi, I am a RoR newbie and I''ve been experimenting with different databases (mySQL, PostgreSQL, etc.) and different table types (MyISAM vs. InnoDB). Is there a preferred database/table type for RoR development. I like how MySQL''s InnoDB tables enforce referential integrity, but these tables require a lot more storage space then MyISAM tables. For everyone with a lot of RoR

i''m using a table, that uses fulltext search and therefore the table type MyISAM everything works fine in production mode, but tests fail with ActiveRecord::StatementInvalid: Mysql::Error: The used table type doesn''t support FULLTEXT indexes when looking in the test db it''s clear, that it''s using InnoDB, but even manually changing the table type does not help,

Hi folks, This latest release of Ferret has a lot of improvements. There have been substantial improvements to performance. Try it for yourself to see. I won''t be publishing any numbers just yet. I will say though that it''s still about 2-4 times slower than Lucene with the extension installed. There is also some performance improvements in the pure Ruby version if you

I''m trying to generate a rails pagination helper for some ferret search results, and I need to know how many total matches there are to my search query. I don''t see an obvious way of finding this. Any help would be appreciated. Thanks, Carl Youngblood

Hi Guys, I just wanted to take a moment to give some positive feedback regarding my experiences with Xapian recently. I've been doing a fair amount of research into search engines recently, as we have some fairly specific requirements with what we're attempting to do with them. Long story short, after a few weeks of playing around with just about everything under the sun (or at least,

Can anyone point me to the proper syntax to build a FULLTEXT MySQL index via migrations? I''m really liking these things, and don''t want to step back into the world of manual intervention.

I''m noticing some long delays when optimizing my index. I know this is terribly inefficient, but in order to make sure that my ActiveRecord model is in sync with my index, I''m optimizing after every new record that I store, like so: class Resume < ActiveRecord::Base include Ferret has_and_belongs_to_many :users SEARCH_INDEX = File.dirname(__FILE__) +

I seem to be getting the same document multiple times in my search results. I''m wondering if this is because by default a document is placed in the search results every time the word you''re looking for shows up. Is that the way it works? Thanks, Carl

I have an index in which I want different records to be accessible to different users. I think I can do this by adding a "users" field to each record in the index and narrow down my queries to only those records matching the current user''s userid. I have the userids separated by commas. What would be the right way to query for a certain user? I have to make sure that I

I''m noticing that ferret-write.lck sometimes stays in my index directory and throws exceptions whenever someone tries to do a search. Apparently there are some cases where ferret doesn''t realize that the file is old and can be deleted. I''m wondering what the best way to recover from this error is. Am I safe just writing a cron job that deletes this file if it is over

Up to now in my ferret development I have been using simple single-word strings as my search queries. I just now am trying to increase the complexity of my queries. When I was passing a single word with no spaces in my index searches, like so: count = index.search_each(''testing'') do |d, s| ... end everything worked fine. But now when I do something like this: count =

I have a model class in rails that has a class variable that is a ferret index. For some reason, the methods in my class that refer to the class variable are getting lock conflicts. Can anybody see any obvious reason why? I notice that it keeps leaving a lock file in the index directory. I thought auto_flush was supposed to remove the lock automatically after every operation. Is there

I''ve been creating my tables using the command line approach Dave advocates in AWD. I just noticed that they''re being created as MyISAM-type tables. I remember reading (but not where) that I should be creating these as InnoDB-type tables. So, two questions... 1) Is the table type important? (a "why" component to the answer would be nice too ;-) ) 2) If so, is

Hey folks, A lot of confusion has been caused by having stop-words filtered by the default analyzer. There have been a few suggestions to remove this feature so I thought I''d put it to a vote. Making this change would not be backwards compatible and would require users to either rebuild their indexes or change their code to keep the same stop-words settings. However, it would save a lot

I''m getting a locale not set error. Does anyone know how I should set my locale in my rails environment so that ferret knows what to do? Why isn''t this a problem in the ruby version of ferret? Thanks, Carl

Hi All, In my companies environment, we have multiple sites in multiple geographic locations, sometimes with high latency between the sites. I''m trying to come up with a solution that could provide puppet infrastructure to all sites nodes. ----a few assumptions--- - puppet manifest / configuration is fetched from a centralized version control system. - store db is needed (ssh keys,