Hi!

On Fri, Sep 01, 2006 at 02:16:17PM +0200, Andy Kuo wrote:
[..]
> 
> On the Linux box, MySQL was complaining about an "unknown column 
> Foos.id".  I hadn't realized that MySQL on Linux was case-sensitive, 
> whereas Windows is not, so I changed the line to
> 
> conditions = [ "#{self.name.downcase.pluralize}.id in (?)", id_array ]

Even better would be "#{self.table_name}.id in (?)", because that works in
case you don't use the standard naming scheme for your tables, too.
Recent versions of aaf contain this fix.

> 2. I had defined a WhiteSpaceAnalyzer (different from the one defined in 
> Ferret) in my environment.rb file, and was calling it in acts_as_ferret. 
> For some reason, though, the analyzer being used was the 
> WhiteSpaceAnalyzer defined in Ferret, instead of mine.  My guess as to 
> why this is happening is because of the order in which environment.rb 
> and ferret are loaded?  I'm not even sure redefining it in 
> environment.rb is the right way to do it, so I'd be happy if someone 
> knew what the right way of doing this is.  My workaround was just to 
> rename my analyzer.

where you declare you custom Analyzer class shouldn't be that important,
I'd personally place it in lib/ and require that file in environment.rb.

To avoid problems you should indeed choose a unique class name, though I
can't imagine where the problem was in that special case.

Jens


-- 
webit! Gesellschaft für neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer       [EMAIL PROTECTED]
Schnorrstraße 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to