On Thu, May 21, 2009 at 11:41:50AM -0700, [email protected] wrote: > > This known issue that if email is not in the db then result would be > > empty even if condition is ORed with another, but believe me correct > > query will kick breath out of your DB server. > > > > Are you saying that this "known issue" is a bug or is it intentional? > > I know that with a ton of tickets, this kind of "search everything" is > not practical. But this will be a new RT deployment and I need to ease > the support staff (and the boss) into getting used to this new system. > Eventually I know they will find the QueryBuilder screen to be very > precise and great, but right now everything is new and different and > that screen scares them. They think it's too complicated. > > That's why I'd like to get the "WHERE EmailAddress like '%foo%' OR > 'Content like '%foo%' OR'd together instead of having the EmailAddress > separated from the rest of the query by an "AND." > > Thanks, > > A.
Allen, This will result in every search being a full scan of the database looking for a match in the content. This will cripple your system for all but the smallest of databases. If you really intend to search in the content, please choose and use a database backend that supports full-text indexing. I know that the wiki has recipes for Oracle and PostgreSQL. Cheers, Ken _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
