sup

commit b06a8dccf2572d3ac6b99bdb7519ff6e8b85c3f9
parent a57e59d2566ddf6ed817e952759b2cce2eae8d87
Author: William Morgan <wmorgan-sup@masanjin.net>
Date:   Sun, 24 Feb 2008 20:53:23 -0800

only use the first 255 characters of a message id (ferret bug workaround)

Apparently, constructing a TermQuery object with a field value of more than
255 characters never successfully matches.

This is not a good long-term solution. A good one would be to take the SHA1
of every message id instead. That will require an index rebuild, so I will
save that patch until later.

Diffstat:

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/sup/message.rb b/lib/sup/message.rb
@@ -148,7 +148,7 @@ class Message
     @source.fn_for_offset @source_info
   end
 
-  def sanitize_message_id mid; mid.gsub(/\s/, "") end
+  def sanitize_message_id mid; mid.gsub(/\s+/, "")[0..254] end
 
   def save index
     return unless @dirty