trying to set up a View using:

- search api - latest dev
- search views
- search db - latest dev

loosely following this guide: http://drupal.org/node/1597930 except for the filter for Indexed node as this doesn't exist.

so i have this: http://screencast.com/t/e2qvY1Ou

CommentFileSizeAuthor
#18 1805640-18--fulltext_missing_facets.patch812 bytesdrunken monkey
#9 search_api_db-unknown_column_value-1805640-9.patch444 bytessemiaddict

Comments

liquidcms’s picture

liquidcms commented
Priority: Normal » Major

bumping to major since as far as i can see nothing works with this error occurring. perhaps this is more on the search db module than on search api in general. going to try solr to see if that works any better.

lefnire’s picture

lefnire commented

Same issue for me, and I also think it might be search_api_db, I posted there: #1807622: Fix definition of the default node index

liquidcms’s picture

liquidcms commented

is it just me or have error msgs become completely useless in D7?? lol - no file or line number; how is someone supposed to debug this?? grrr!!

sardbaba’s picture

sardbaba commented

same issue here.

liquidcms’s picture

liquidcms commented

i do have all of this working now. :)

i have:
Search API 7.x-1.2+9-dev (2012-Oct-10)
Search API Database Search 7.x-1.0-beta3+4-dev (2012-Jul-01)

sardbaba’s picture

sardbaba commented

Yep, me too :)
I really don't know why, probably I have misconfigured something... but following carefully this tutorial:
http://envisioninteractive.com/drupal/drupal-7-views-with-faceted-filters-without-apachesolr/
solves my problem.

I've changed the project and closed.

Cheers

maxplus’s picture

maxplus commented
Project: Search API » Search API Database Search
Version: 7.x-1.x-dev » 7.x-1.0-beta4
Component: Views integration » Code
Status: Active » Closed (works as designed)

Hi,
I had the same problem and it was solved by setting the Node Title field to string instead of full text in the Search API setup page.

MrHertal’s picture

MrHertal commented

Thanks a lot maxplus, that solved my problem too.

semiaddict’s picture

semiaddict commented
Status: Closed (works as designed) » Needs review
StatusFileSize
new search_api_db-unknown_column_value-1805640-9.patch444 bytes

I had the same issue, and needed to keep the fields as fulltext for different reasons.
After some digging, I think I found the source of the problem. It should be fixed with the attached patch (for 7.x-1.0-beta4).

ntigh52’s picture

ntigh52 commented

#7 thanks
#9 thanks
B-I-N-G-O!!!
Thanks, solved my problem!!
Thanks a lot!

Slacky08’s picture

Slacky08 commented

#7 worked for me too, but it wasn't the Node Title I was using so I just changed my other field to be "string" rather than "full text".

Thanks,

Rich

BParticle’s picture

BParticle commented

#9 works, great!

maximpodorov’s picture

maximpodorov commented
Status: Needs review » Reviewed & tested by the community

#9 works, really.

andypost’s picture

andypost
he/him
Primary language Russian
commented
Version: 7.x-1.0-beta4 » 7.x-1.x-dev

Really annoying

maximpodorov’s picture

maximpodorov commented
Status: Reviewed & tested by the community » Needs work

Another issue:
I created aggregated field with one underlying field - node title (with aggregation type: 'First'), added this new field to index as String (not Full text). Reindexing failed with the following message:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'word' in 'field list'

LeviThomason’s picture

LeviThomason commented

Also confirming #9 works for the originally posted issue. Not sure about the issue in #15.

cafuego’s picture

cafuego commented
Status: Needs work » Reviewed & tested by the community

The patch in #9 fixes search_api_pages and search_api views for me.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Title: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'value' in 'where clause' » Fix improper handling of "missing" facets for fulltext fields
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new 1805640-18--fulltext_missing_facets.patch812 bytes

Ah, thanks for reporting this and spotting the problem.
However, I think the proper fix is the one in the attached patch. We actually want to treat text fields exactly like multi-valued fields, as their tables also don't have NULL entries.

@ maximpodorov: Please create a new issue (or find one really discussing yours) for your problem if it's, as you say yourself, another issue.

Adam Wood’s picture

Adam Wood commented

The patch in #18 fixed the same SQLSTATE[42S22] error mentioned above when indexing full text fields from the Location module.

Be sure to disable the module, re-enable it, run update.php, and rebuild the index.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Status: Needs review » Fixed

Great, thanks for testing!

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.