[ 
https://issues.apache.org/jira/browse/OFBIZ-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875180#action_12875180
 ] 

Jacques Le Roux commented on OFBIZ-3789:
----------------------------------------

Not sure it's related but using Postgres I get this

2010-06-03 18:13:16,609 (http-0.0.0.0-28443-5) [    
ConfigXMLReader.java:120:INFO ] controller loaded: 0.031s, 466 requests, 144 
views in jndi:/0.0.0.0/catalog/WEB-INF/controller.xml
2010-06-03 18:13:16,625 (http-0.0.0.0-28443-5) [     
RequestHandler.java:741:INFO ] Rendering View [keywordsearch], 
sessionId=35798BDD7FF98064A8A757E3C135DC27.jvm1
2010-06-03 18:13:16,718 (http-0.0.0.0-28443-5) [      
ScreenFactory.java:128:INFO ] Got 5 screens in 0.015s from: 
file:/D:/workspace/ofbizDev/applications/product/widget/catalog/FindScreens.xml
2010-06-03 18:13:16,734 (http-0.0.0.0-28443-5) [  
KeywordSearchUtil.java:235:INFO ] Expanded keyword [gz], got set: []
2010-06-03 18:13:16,734 (http-0.0.0.0-28443-5) [      
ProductSearch.java:271:INFO ] Finished initial setup of keywords, 
doingBothAndOr=false, andKeywordFixedSet={%gz%}
 keywordFixedOrSetAndList={}
2010-06-03 18:13:16,734 (http-0.0.0.0-28443-5) [      
ProductSearch.java:654:ERROR]
---- exception report ----------------------------------------------------------
Error in product search
Exception: org.ofbiz.entity.GenericDataSourceException
Message: SQL Exception while executing the following:SELECT DISTINCT 
PK1.RELEVANCY_WEIGHT, PROD.PRODUCT_ID FROM (public.PRODUCT PROD LEFT OUTER JOIN 
public.PRODUCT_CALCULATED_INFO PRODCI ON PROD.PRODUCT_ID =
PRODCI.PRODUCT_ID) INNER JOIN public.PRODUCT_KEYWORD PK1 ON PROD.PRODUCT_ID = 
PK1.PRODUCT_ID WHERE ((PK1.KEYWORD LIKE ?)) ORDER BY TOTAL_RELEVANCY DESC 
(ERREUR: la colonne ½ total_relevancy ╗ n'existe pas)
---- cause ---------------------------------------------------------------------
Exception: org.postgresql.util.PSQLException
Message: ERREUR: la colonne ½ total_relevancy ╗ n'existe pas
---- stack trace ---------------------------------------------------------------
org.postgresql.util.PSQLException: ERREUR: la colonne ½ total_relevancy ╗ 
n'existe pas

(n'existe pas = does not exist)

I can see the totalRelevancy in ProductSearch.java

HTH

> No results when searching with keywords in catalog
> --------------------------------------------------
>
>                 Key: OFBIZ-3789
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3789
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Erwan de FERRIERES
>            Assignee: Adam Heath
>             Fix For: SVN trunk
>
>
> Steps to reproduce :
> go to : https://localhost:8443/catalog/control/keywordsearch
> then in the Keywords textbox, type GZ, then hit enter key.
> No results are shown.
> Log error in the console :
> 2010-05-28 16:03:07,780 (http-0.0.0.0-8443-1) [      
> ProductSearch.java:271:INFO ] Finished initial setup of keywords, 
> doingBothAndOr=false, andKeywordFixedSet={%gz%}
>  keywordFixedOrSetAndList={}
> 2010-05-28 16:03:07,849 (http-0.0.0.0-8443-1) [      
> ProductSearch.java:654:ERROR] 
> ---- exception report 
> ----------------------------------------------------------
> Error in product search
> Exception: org.ofbiz.entity.GenericDataSourceException
> Message: SQL Exception while executing the following:SELECT DISTINCT 
> PK1.RELEVANCY_WEIGHT, PROD.PRODUCT_ID FROM (OFBIZ.PRODUCT PROD LEFT OUTER 
> JOIN OFBIZ.PRODUCT_CALCULATED_INFO PRODCI ON PROD.PRODUCT_ID = 
> PRODCI.PRODUCT_ID) INNER JOIN OFBIZ.PRODUCT_KEYWORD PK1 ON PROD.PRODUCT_ID = 
> PK1.PRODUCT_ID WHERE (PK1.KEYWORD LIKE ?) ORDER BY TOTAL_RELEVANCY DESC 
> (Column 'TOTAL_RELEVANCY' is either not in any table in the FROM list or 
> appears within a join specification and is outside the scope of the join 
> specification or appears in a HAVING clause and is not in the GROUP BY list. 
> If this is a CREATE or ALTER TABLE  statement then 'TOTAL_RELEVANCY' is not a 
> column in the target table.)
> ---- cause 
> ---------------------------------------------------------------------
> Exception: java.sql.SQLSyntaxErrorException
> Message: Column 'TOTAL_RELEVANCY' is either not in any table in the FROM list 
> or appears within a join specification and is outside the scope of the join 
> specification or appears in a HAVING clause and is not in the GROUP BY list. 
> If this is a CREATE or ALTER TABLE  statement then 'TOTAL_RELEVANCY' is not a 
> column in the target table.
> ---- cause 
> ---------------------------------------------------------------------
> Exception: org.apache.derby.impl.jdbc.EmbedSQLException
> Message: Column 'TOTAL_RELEVANCY' is either not in any table in the FROM list 
> or appears within a join specification and is outside the scope of the join 
> specification or appears in a HAVING clause and is not in the GROUP BY list. 
> If this is a CREATE or ALTER TABLE  statement then 'TOTAL_RELEVANCY' is not a 
> column in the target table.
> ---- cause 
> ---------------------------------------------------------------------
> Exception: org.apache.derby.iapi.error.StandardException
> Message: Column 'TOTAL_RELEVANCY' is either not in any table in the FROM list 
> or appears within a join specification and is outside the scope of the join 
> specification or appears in a HAVING clause and is not in the GROUP BY list. 
> If this is a CREATE or ALTER TABLE  statement then 'TOTAL_RELEVANCY' is not a 
> column in the target table.
> ---- stack trace 
> ---------------------------------------------------------------
> ERROR 42X04: Column 'TOTAL_RELEVANCY' is either not in any table in the FROM 
> list or appears within a join specification and is outside the scope of the 
> join specification or appears in a HAVING clause and is not in the GROUP BY 
> list. If this is a CREATE or ALTER TABLE  statement then 'TOTAL_RELEVANCY' is 
> not a column in the target table.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to