> On 4 Feb 2016, at 10:21, Palle Girgensohn <gir...@pingpong.net> wrote: > > > > 4 feb. 2016 kl. 00:48 skrev David Gwynne <da...@gwynne.id.au>: > >> >>> On 4 Feb 2016, at 00:08, Palle Girgensohn <gir...@pingpong.net> wrote: >>> >>> Hi David, >>> >>> Thanks for this input. >>> >>> it takes the query from 1 minute+ (== timeout in fcgid) to subseond. >>> >>> Big leap forward! >>> >>> Thanks! >>> >>> >>> The two queries you posted are equally fast for me, ~ 8 ms, but render >>> different result, 15 vs 16 rows. :-( >> >> yeah, after i sent it i recognised some issues with mine. i can fix it, but >> then id have to go back and make RT generate the query and that idea makes >> me sad. >> > > Mmm, the problem is really the ORM. It never really marries well with SQL. > Sets vs objects. Sadly, I don't think it'll be worth the effort trying to > force RT to generate the query. But my experience with this specific > implementation is limited. > > >> if there's interest i can fix my query, but only if it'll help someone else > > I'm happy with the first advice, reverting the patch. It made RT usable from > not being that! :-) > > Btw, already had AutocompleteOwnersForSearch enabled.
and you still got hit with the slow query? --------- RT 4.4 and RTIR Training Sessions (http://bestpractical.com/services/training.html) * Hamburg Germany March 14 & 15, 2016
