On 12 May 2010 08:09, Pat Allan <[email protected]> wrote: > Ah, I'd forgotten index does its own conf file generating, it doesn't call > the configure rake task... I wanted to make sure the error was in writing > the file instead of reading it. >
Ah I see. If I run ts:config it creates the file or overwrites the existing one. The same happens if I run ts:index. > So, two things: what happens when you delete (or maybe just rename) the > existing conf file? If I delete the file it just creates a new .conf file when I run ts:index. > And what's the stack trace from the rake task? Seems it's missing from the > output below. What is in the previous email is all that comes with the --trace option, there are no stack trace. Only other log information is this in my /log/development.log when I run ts:index I get; [4;36;1mSQL (0.0ms) [0m [0;1mSET NAMES 'utf8' [0m [4;35;1mSQL (0.0ms) [0m [0mSET SQL_AUTO_IS_NULL=0 [0m [4;36;1mSQL (0.0ms) [0m [0;1mSHOW TABLES [0m [4;35;1mIngredient Columns (4.0ms) [0m [0mSHOW FIELDS FROM `ingredients` [0m [4;36;1mSQL (0.0ms) [0m [0;1mSELECT @@global.sql_mode, @@session.sql_mode; [0m Cheers -- 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.
