Hmm, it's odd that it's using the MySQL functions - there is  
PostgreSQL functions that do the same thing (well, TS creates one to  
help with things) - see postgresql_adapter.rb in the TS source.

Looking at the DSN in your output, it's using pgsql, but the SQL  
queries don't match. When you're in 'script/console production',  
what's the output of Entry.connection.class.name ?

-- 
Pat

On 11/12/2008, at 6:43 AM, teejayvanslyke wrote:

>
> Greetings,
>
> I'm attempting to run the indexer on a PostgreSQL configuration, but
> am running into the following error:
>
> $ rake RAILS_ENV=production thinking_sphinx:index
> indexer --config ****/config/production.sphinx.conf --all
> Sphinx 0.9.8.1-release (r1533)
> Copyright (c) 2001-2008, Andrew Aksyonoff
>
> using config file '****/config/production.sphinx.conf'...
> indexing index 'entry_core'...
> ERROR: index 'entry_core': sql_range_query: ERROR:  syntax error at or
> near "SEPARATOR"
> LINE 1: ..."entries"."id", CAST(GROUP_CONCAT("lemmas"."text"
> SEPARATOR ...
>                                                             ^
> (DSN=pgsql://lang:*...@****:5432/****).
> total 0 docs, 0 bytes
> total 0.019 sec, 0.00 bytes/sec, 0.00 docs/sec
> distributed index 'entry' can not be directly indexed; skipping.
>
> (I've censored some directory paths and hostnames above with ****)
>
> If I remember correctly from my Ultrasphinx days, there was a
> migration which added stored procedures like GROUP_CONCAT to the
> PostrgeSQL database.  I see no similar mechanism for Thinking
> Sphinx.
>
> For what it's worth, I'm running PostgreSQL 8.3.4.  Any assistance
> would be greatly appreciated!
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to