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 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" sort by custom field feature doesn't work, At > ALL. > 3) When deleting fields from the default display of choices, we must > do > so one field at a time. Very time-consuming and ANNOYING! Why can't we > just highlight the ones we want to delete (like the ones we choose to > add from the left side) and do it in one swell foop (he he). > > On Reminders; we think it would be REALLY convenient for Reminders to > automatically resolve if the ticket they are linked to gets resolved. > Actually, we can't think of a reason to NOT have done this in the origin > design. > > So, other than having to re-login the first time we try to do > something > after the initial sign on, AND the above-mentioned problems with query, > we like it just fine (come on in! The water is just "ffffiiiiiinnnnneee" > - an old Cosby joke). > Are there any fixes (for any of the above) about ready to implement? > > > Kenn > LBNL > > Ruslan Zakirov wrote: > > 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 = 'Y'" > > and most probably other where condition on watcher is joined with > > another condition using OR aggregator. > > > > We have two ways to fix the problem. I sent one patch already to the > > list, but we really need more feedback (positive or negative) to make > > right choice, so I post it again. > > > > Please do the following steps to collect feedback I need. > > 1) build a query (see above) in the query builder using sane values > > for your setup > > 2) execute search and wait for results, we expect it to be very slow, > > so you shouldn't wait to much > > 3) apply the patch > > cd /opt/rt3; > > cat /path/to/the/patch | patch -p0 > > 4) stop and start web server > > 5) try search again > > > > Send feedback. People who know how to deal with slow-logs, explain are > > more than welcome to send additional info, but even if you don't know > > how to deal with those it's ok, just send description of the system > > behavior and wallclock timings. > > > > 6) revert patch > > cat /path/to/the/patch | patch -p0 -R > > 7) stop and start web server > > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 > _______________________________________________ > 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 > -- Best regards, Ruslan. _______________________________________________ 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