Closed (fixed)
Project:
Fuzzy Search
Version:
7.x-1.x-dev
Component:
Search API integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Oct 2011 at 11:50 UTC
Updated:
15 May 2013 at 21:58 UTC
I'm not sure if this is a Fuzzy Search or Search Api issue:
If i try to index only the title as String i can't index my entries. In the log this error apperas:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'value' in 'field list'
If i try to index the title as fulltext, i get this error when i try to create an index view:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'percent' in 'order clause'
My specifications:
Core: 7.8
Search API 1.0 Beta 10
Fuzzy Search: 1.x-dev
core module: Locale active (among others)
Thanks
Comments
Comment #1
awolfey commentedRechi, can you update everything and confirm that this still exists, if you're still using fuzzysearch? Thanks.
Comment #2
xbrianx commentedI am getting something similar trying to use Fuzzy Search when creating a view.. My views preview gives me an error "SQLSTATE[42S22]: Column not found: 1054 Unknown column 'percent' in 'order clause'"
Comment #3
xbrianx commentedTo remove this error I needed to add a filter in views.
Comment #4
awolfey commentedI'm going to close this. For the views issue see #1472116: Views Search Error :createKeysQuery.
Comment #5
Cablestein commentedFor me, the moment I added a sorting (not a filter) on the View, this error went away.
Comment #6
hedel commentedI'm not using views with Fuzzy Search, only Search Page. Is working the module and let me search, the problem is if I put less than 3 letters in the search input answer this error:
For example: if I put 'pro' find all possible combinations, but with 'p' or 'pr' answet this mistake.
For other side, I add in kategories terms in the index, but is not include in the result of searching.
My config:
Comment #7
sijuwi commentedI'm getting the following when I try to index on the status page:
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE (item_id = '3173')' at line 1Comment #8
seanbThis error occurs for me too when searching for terms with 1 or 2 letters. If you enter more letters there is no problem.
It looks like the search key gets filtered if it's shorter then the setting in the fuzzysearch server (check the splitKeys function in service.inc), but there is no error thrown and/or empty result set given back.
I fixed the issue by returning an empty result set if there are no key's, or no valid keys in the search() function.
Change line 629 - 632:
Comment #9
Sborsody commented@sijuwi, try applying the patch for search_api_db service.inc file at http://drupal.org/node/1346846#comment-5574146 manually to the fuzzysearch service.inc file in fuzzysearch/includes/. The function FuzzySearchService->indexItem() is basically the same as SearchApiDbService->indexItem().
Comment #10
Sborsody commented@sijuwi,
Scratch that. Install this patch for search_api instead: http://drupal.org/node/1414138#comment-6017252. See my comments on that issue at http://drupal.org/node/1414138#comment-6207610
Comment #11
sijuwi commentedThanks, will do
Comment #12
quickly commentedI tried both #9 and #10 separately but none of them worked for me...
Comment #13
Sborsody commentedKeep in mind that #9 and #10 are in response to #7. The SQLSTATE error message in #7 is indicative of a different problem from the one presented in the original post.
Comment #14
devyd commentedSQLSTATE[42S22]: Column not found: 1054 Unknown column 'percent' in 'order clause'On a fresh module installation inside a d7search distro.
Also disappeared for me like in #5, adding a 'sort by relevance' to the view. Prior to that, the views query would not be valid.
Comment #15
awolfey commentedThanks seanB, a fix is committed. This fix isn't tested in views. There are a lot of unrelated or slightly related views errors mentioned above. Please search the issue queue and create a new issue if you can't find an existing one.
Comment #17
Funksmaname commented#14 solved the issue for me - thanks devyd!