Hi, brave users of RT 3.6.4.
In the mentioned version of RT I changed SQL queries we generate to
searches tickets by watchers(requestors, cc or admicc). Logic of those
queries is better now. However, I've broken performance of queries
like Requestor = 'X' OR Owner = 'Y', Requestor = X OR Status =
For me, this patch has worked perfectly. Right after my upgrade to 3.6.4,
I had posted to this list regarding search timeouts when using AdminCC or
CC searches, but got no response. Eventually, other folks started to have
the same problem and as it turns out, it's only when using the 'OR'
Ruslan,
We just installed 3.6.4 in our test environment and have found a few
problems with the Query:
1) Although OwnerName appears as a field to display, it is not
included into the choices for a sort. Custom.Owner doesn't work worth
a [EMAIL PROTECTED]^%.
2) The highly-touted
Rus;
Just applied the patch a query similar to the below:
- before the patch I stopped it after 3 minutes no results,
- after the patch it returned the correct results within seconds ..
Regards;
Roy
James Moseley wrote:
( Status = 'new' OR Status = 'open' ) AND ( Cc.Name = 'user' OR
Kenneth, don't you know that sending unrelated things to a thread on
mailing lists is very bad habit. Sorry, but I ignore this mail as it
has nothing to do with the patch.
On 8/3/07, Kenneth Crocker [EMAIL PROTECTED] wrote:
Ruslan,
We just installed 3.6.4 in our test environment and
