search for: query_strings

On Sun, Sep 30, 2018 at 09:50:30AM +0100, James Aylett wrote: > Note that I'm using 1.4.7, and from your output I believe you're not > (the * in the query description I believe doesn't happen in those > situations any more). 1.4.4 and later eliminate redundant 0 scaling factors, but this one isn't actually redundant: > > Query(((Tmail AND 0 * XSUBJECTnot at 1)

Hi, I wonder if it is possible to perform the "find_by_contents" on a subset of fields indexed in acts_as_ferret.If so, how? In my code I have: acts_as_ferret (:fields => [''title'', ''focus'', ''purpose'']) However, I like to have two search options one on all fields and one only on the title. Any help is most appreciated.

I'm having trouble getting a search via php working, I get the following error: *Fatal error*: No matching function for overloaded 'QueryParser_parse_query' in */usr/local/share/php5/xapian.php* on line *1409 *The error occurs at this code $query = $qp->parse_query( $query_string , XapianQueryParser::FLAG_PHRASE |

Hi Zed/Jonathan, VMWare Server is free now. http://www.vmware.com/products/server/ http://www.vmware.com/pdf/server_datasheet.pdf www.vmware.com/download/server Runs on any standard x86 hardware * Supports 64-bit guest operating systems, including Windows, Linux, and Solaris * Support for VMware VirtualCenter to efficiently manage infrastructure from a central management console *

On Sun, Sep 30, 2018 at 09:05:25AM -0300, David Bremner wrote: > if (str.find (' ') != std::string::npos) > query_str = '"' + str + '"'; > else > query_str = str; > > return parser.parse_query (query_str, NOTMUCH_QUERY_PARSER_FLAGS, term_prefix); I wouldn't recommend trying to generate strings to feed to

Hello Everyone, I just posted another pre-release of Mongrel that fixes a bug which caused Mongrel to claim it was getting parsing errors because the QUERY_STRINGs were too long. In actuality it was shift in the parser that made empty queries (/test?) become negative. This is fixed up now. Here''s the full list of changes: * It has a couple of fixes for win32, but I still have to apply a few more patches from Jan Svitok. This will happen tonight....

Hello, There is a build error by what looks to be a typo in xapian-applications/omega/omega.cc My checkout is about 15 minutes old, so it's possible it has been caught since then. omega.cc: In function ?int main(int, char**)?: omega.cc:204: error: ?pretty_tery? was not declared in this scope make[3]: *** [omega.o] Error 1 make[3]: Leaving directory

About 17:00 localtime I managed to get fastcgi, Rails and IIS all happy together. Upon success I ripped off my clothes and ran through the village yelling "The future is now!". A PDP-11 geezer stuck his head out a window and said "The future isn''t what it used to be and keep yer shirt on". Modifications were required to dispatch.fcgi and request.rb. The following

I''ve read about the problems of using page cache when there''s a query string, i.e. /article/list?page=1 will cache /article/list.html, then /article/list?page=5 will retrieve /article/list.html regardless of query string. I''m using a workaround, it looks almost obvious but since I haven''t found it mentioned anywhere I''m afraid there''s some

query strings built by R method can''t handle multiple values from checkbox selections R(SomeRoute, :reply_status=>%w{1 2 4}) should return query_string=" http://localhost:3301/someroute/?reply_status_id=1&reply_status_id=2&reply_status_id=4 " qsp(query_string) -> {"reply_status_id"=>["1", "2", "4"]} from

Anyone know how to stub Kernel#open? I''m trying to mock/stub an open-uri call, but it doesn''t seem to like it. Here''s the test code, and the failures: body = File.open(File.dirname(__FILE__) + ''/../fixtures/google_search_california.html'').read

Hello all, Quick question (possibly!) - I''ve got a few records indexed and doing a search for ''test'' reports in no hits even though I know the word ''tests'' exists in the indexed field. Doing a search for ''tests'' produces a result. I would have thought that ''test'' would match ''tests'' but no such

We are using the --enable-maintainer-mode and will move to git soon. The diff file is attached. *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 8:26 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:48, Pallavi

My code is not on Github. I am using the tarball as of now. The following it the error that occurred: http://pastebin.com/cVJrjUZX On Sun, Apr 13, 2014 at 8:16 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:37, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > A linker error is encountered even after following the above

Hello, this is probably trivial but I failed to find this particular snippet of code. What I got: my_dataframe (contains say a 40k rows and 4 columns) distances (vector with euclidean distances between a query vector and each of the rows of my_dataframe) What I do: after scaling data my_dataframe I calculate distances. order them then extract top five hits my_dataframe <-

Hi guys, Is there some way of getting ferret matches string, when i do a fuzzy search? The scenario is this: 1. The user search for ''show'' 2. Nothing was found 3. So I do a fuzzy search, passing ''show~'' 4. It gives me somes results, most of all was matched with ''showcase'' 5. So I want to tell the user that: Nothing was found with

Olly Betts <olly at survex.com> writes: > > FWIW, I also couldn't reproduce this (I tried with quest and 1.4.7): > > $ quest -psubject:S -fdefault,boolean_any_case 'subject:"and"' > Parsed Query: Query(Sand at 1) > Ah, OK, it must have something to do with the way that notmuch is using field processors. And I see now that the following code (from

Probably an uncaught malformed query - the following form of search queries causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled): x-y NEAR test NEAR test The first term can be anything with a hyphen in it but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a

--- search-xapian/XS/QueryParser.xs | 6 ++++++ search-xapian/Xapian/QueryParser.pm | 7 +++++++ xapian-core/include/xapian/queryparser.h | 3 +++ xapian-core/queryparser/queryparser.cc | 6 ++++++ xapian-core/queryparser/queryparser.lemony | 9 +++++++++ xapian-core/queryparser/queryparser_internal.h | 4 +++- 6 files changed, 34

Hey all, First off, thanks to Rick Olson and whoever else was involved with this plugin... It''s been amazingly easy to implement. I''ve got a question about the path_info parameter, though... It seems that unless the request PATH_INFO exactly matches the path_info passed in to the plugin at inclusion, it won''t actually trigger Add and add the upload to the list of