<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="font-family: -webkit-monospace; font-size: 10px; ">I appreciate the advice about searches and we're aware of the impact on performance.<br><br>Before posting here I had searched through the archives and was unable to find any solutions specific to 3.8.2 (or perhaps I'm not searching for the right keywords in the vast amount of data therein?). I'd rather not modify the core code if possible so we do not run into problems (or loss of functionality) in subsequent upgrades. Isn't there any way to override this behavior without modifying the base code?<br><br>Looking though the code (specifically Search/Simple.html) I see references to a "SearchArgs" callback, but I'm not clear as to what that is or how it's used. Perhaps this is simply a red herring to my question.<br><br>I had hoped this could be a simple thing to change considering it's pulling the default search criteria from somewhere. When I go to "Edit Search" after performing a SimpleSearch I see the query has inserted;<br><br>"( status = 'new'<br> OR status = 'open'<br> OR status = 'stalled'"... etc<br><br>into the query (which are the active statuses listed in the @ActiveStatus array in RT_SiteConfig.pm). We simply want to remove this portion from the default search criteria.<br><br>I'm still hopeful someone will be able to point me in the right direction.<br><br>Thanks again,<br><br>Donovan<br></span><div><div><br></div><div>On Apr 7, 2009, at 2:05 PM, Kenneth Marshall wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Tue, Apr 07, 2009 at 01:55:19PM -0400, Jerrad Pierce wrote:<br><blockquote type="cite">On Tue, Apr 7, 2009 at 13:43, Donovan Young<br></blockquote><blockquote type="cite"><<a href="mailto:dyoung-rtusers@techsafari.com">dyoung-rtusers@techsafari.com</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">We've recently upgraded to 3.8.2 from 3.6.3 and originally the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">SimpleSearch feature would search all tickets (active and inactive)<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please see the list archives.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It really is best to search active tickets only, but you probably want<br></blockquote><blockquote type="cite">to add one of<br></blockquote><blockquote type="cite">the patches to allow you to modify a search to target<br></blockquote><blockquote type="cite">active/inactive/any tickets.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-- <br></blockquote><blockquote type="cite">Cambridge Energy Alliance: Save money. Save the planet.<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a><br></blockquote><blockquote type="cite"><br></blockquote><br>I will second the comment about searching active tickets only. In particular<br>the fulltext:word option will have a (ahem) dramatic affect on the I/O load<br>of your database if you are not using a system that supports full-text<br>indexing. Limited to active tickets might me manageable, but all tickets is<br>a problem that gets worse and worse as new tickets continue to be added.<br>Just how many sequential scans of your database can your backend support? :)<br>Currently, Oracle and PostgreSQL support full-text indexing with RT.<br><br>My two cents.<br>Ken<br></div></blockquote></div><br></body></html>