?
avatar ralain
ralain
20 Dec 2016

Steps to reproduce the issue

Apply PR #13291 which fixes another search related issue.
Add a Search module (not Smart Search) and use it to search for any word.

Expected result

No error.

Actual result

screen shot 2016-12-20 at 16 06 14

Additional comments

Examining the debug information we see that the error is caused by comparing two column of different types, #__fields_values.item_id (varchar) and #__content.id (integer), which can't be done on PostgreSQL without typecasting.

@laoneo I presume there was a reason for making #__fields_values.item_id column a varchar, like enabling support for third party extensions with non-numerical ids?

screen shot 2016-12-20 at 16 04 09

avatar ralain ralain - open - 20 Dec 2016
avatar joomla-cms-bot joomla-cms-bot - change - 20 Dec 2016
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 20 Dec 2016
avatar alikon
alikon - comment - 20 Dec 2016

reviewing the query as is issued only for the context context = 'com_content.article'
the fast fix should be a cast....

avatar alikon
alikon - comment - 20 Dec 2016

@ralain now #13291 fix with typecasting can you test...

avatar zero-24 zero-24 - change - 20 Dec 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-12-20 19:05:25
Closed_By zero-24
avatar zero-24 zero-24 - close - 20 Dec 2016

Add a Comment

Login with GitHub to post a comment