search for: handle_parse_errors

Displaying 5 results from an estimated 5 matches for "handle_parse_errors".

2006 Dec 08
6
QueryParser Exception Handling Problem
According to the following link: http://ferret.davebalmain.com/api/classes/Ferret/QueryParser.html :handle_parser_errors => true is enabled by default and seems to be in acts_as_ferret in class_methods.rb of the plugin. However, when I pass a special character as a query (e.g., !, -, <, >, etc) it throws an error and pukes. -- snip -- Error occured in src/q_parser.y:279 - yyerror
2007 Mar 12
5
index.rb:384 [BUG]
...../index/development/article", :create_if_missing=>true, :default_field=>["title"], :analyzer=>#<Ferret::Analysis::StandardAnalyzer:0x2b686dc75f78>, :auto_flush=>true, :or_default=>false, :dir=>#<Ferret::Store::FSDirectory:0x2b686dc76748>, :key=>:id, :handle_parse_errors=>true}, @mon_waiting_queue=[]> (it''s ok, seems to run ok! :) >> query = "ruby" => "ruby" >> options ="" (mmmh, just enough! Now.... ) >> index.search_each(query, options) do |doc, score| ?> puts index[doc][:title] >> end...
2007 Mar 31
4
not understanding search results
I''m getting some results that I don''t understand from a search. The code, based on the tutorial, and the results are below. Everything makes sense to me, except the results for the ''title:"Some"'' query. I would think that it should match the first two documents, but not the third. What am I missing here? Thanks for any help! --- code
2006 Oct 16
2
Ferret::QueryParser::QueryParseException
During our last week of Ferret / aaf usage (also our first week of Ferret / aaf usage), I have received 8 messages stating that our app encountered a Ferret::QueryParser::QueryParseException. For instance: A Ferret::QueryParser::QueryParseException occurred in foo#search: Error occurred in src/q_parser.y:279 - yyerror couldn''t parse query "com -- 404". Error message
2007 Nov 13
8
acts_as_ferret : cannot use a customized Analyzer (as indicated in the AdvancedUsageNotes)
Hi all, I cannot make aaf (rev. 220) use my custom analyzer, despite following the indications @ http://projects.jkraemer.net/acts_as_ferret/wiki/AdvancedUsage To pinpoint the problem, I created a model + a simple analyzer with 2 stop words : "fax" and "gsm". test 1 : model.rebuild_index + model.find_by_contents("fax") # fax is a stop word. => I get a