Calling protected_methods.include?('some_string') would never be true in ruby 1.9+, so we must convert them. I choose to_sym and compare with symbol instead of the reverse way, because I hope people could program toward ruby 1.9 instead of the other way around. When 1.8 is nerver concerned, just remove `.map(&:to_sym)'.
This reverts commit b845140. Conflicts: lib/texticle.rb
… so that it matches the FullTextIndex created
Was using #respond_to?(:scope) to determine whether to use it, but that method call returns true in both Rails 2 and Rails 3. The difference is that the method is 'protected' in Rails 2. Using #defined? fixes this.
…n (bringing rails2-compatibility back again)