#6368 NORM Never A: Accidently entering a space character in the search field hides all journal entries

[Zarro Boogs per Child]

#6368: Accidently entering a space character in the search field hides all journal
entries
-------------------------------+--------------------------------------------
  Reporter:  garycmartin       |       Owner:  tomeu                            
      Type:  defect            |      Status:  new                              
  Priority:  normal            |   Milestone:  Never Assigned                   
 Component:  journal-activity  |     Version:  Development build as of this date
Resolution:                    |    Keywords:                                   
  Verified:  0                 |    Blocking:                                   
 Blockedby:                    |  
-------------------------------+--------------------------------------------
Changes (by Eben):

  * owner:  Eben => tomeu


Comment:

 I don't see any harm in this.  leading/trailing whitespace shouldn't
 really have any effect on a search at all.  More importantly when the
 search string is ''just'' whitespace it makes no sense to perform the
 query.  Trimming before making the query sounds like a reasonable solution
 to this problem.

 This brings up an interesting side observation, which is that it would
 also be possible to accidentally add a leading space character to a
 filename.  Is our matching algorithm so strict that it won't match a query
 of "foo" on an entry titled " foo"?  If so, we  should also trim
 whitespace on titles when they are created.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6368#comment:2>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system