Query Builder

RT Users
1

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
’foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

Luke

2

RT version?On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
‘foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

–
Luke

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We’re hiring! Come hack Perl for Best Practical: Careers — Best Practical Solutions

Best regards, Ruslan.

3

Hi.

Ruslan Zakirov wrote:

RT version?

3.4.5>On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
‘foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

–
Luke

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We’re hiring! Come hack Perl for Best Practical: Careers — Best Practical Solutions

–
Best regards, Ruslan.

Luke

4

As I know that happens since 3.0.x and as I remeber that somehow
related to the code that build next/prev links. I thought this was
fixed in recent versions. Looks like we need to check that again.On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

Ruslan Zakirov wrote:
RT version?

3.4.5

On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
‘foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

–
Luke

–
Best regards, Ruslan.

–
Luke

Best regards, Ruslan.

5

Hi.

Ruslan Zakirov wrote:

As I know that happens since 3.0.x and as I remeber that somehow
related to the code that build next/prev links. I thought this was
fixed in recent versions. Looks like we need to check that again.

Further to this:
I have a fresh install of 3.4.5.
When I do a query in the query builder for

Created > ‘2006-01-01’

I get 51000 tickets.
Now, if I go to load a ticket, it takes a considerably long time for the ticket to load.
When I’ve loaded the ticket and go back to the listing, click on another ticket, the same thing again. It seems that regardless of the ticket/transactions/attachments length, the actual ticket takes just as long to load as the previous ticket.
This is consistent each time the above is repeated.

The length seems to depend on the number of tickets returned by the query.

Why is that?

Kr.
Luke>On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

Ruslan Zakirov wrote:
RT version?

3.4.5

On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
‘foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

–
Luke

–
Best regards, Ruslan.

–
Luke

–
Best regards, Ruslan.

Luke

6

Hi.

Ruslan Zakirov wrote:

As I know that happens since 3.0.x and as I remeber that somehow
related to the code that build next/prev links. I thought this was
fixed in recent versions. Looks like we need to check that again.

Further to this:
I have a fresh install of 3.4.5.
When I do a query in the query builder for

Created > ‘2006-01-01’

I get 51000 tickets.
Now, if I go to load a ticket, it takes a considerably long time for the ticket to load.
When I’ve loaded the ticket and go back to the listing, click on another ticket, the same thing again. It seems that regardless of the ticket/transactions/attachments length, the actual ticket takes just as long to load as the previous ticket.
This is consistent each time the above is repeated.

The length seems to depend on the number of tickets returned by the query.

Why is that?

Kr.
Luke>On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

Ruslan Zakirov wrote:
RT version?

3.4.5

On 3/23/06, Luke Vanderfluit lvanderf@internode.com.au wrote:

Hi.

I’ve found what appears to be a bug in the query builder.
When I build a query that needs to do search of contents of tickets.
Say, for example, I search all tickets with the following query:

Created > ‘2006-01-01’ AND Content LIKE ‘foo’

that query could take a very long time to complete, which is normal (not
acceptable but OK (-:slight_smile:

After the query has completed I go to delete the “AND Content LIKE
‘foo’” phrase and the query seems to run again!

I’m looking at the mysql processes that are triggered by this behaviour.
It seems like the query builder might be using up resources that it
shouldn’t need to.

Can anyone confirm this behaviour? That changing the composition of the
query actually causes the query to run again?

Thanks.
Kind regards.

–
Luke

–
Best regards, Ruslan.

–
Luke

–
Best regards, Ruslan.

Luke

file:///C|/DOCUME%7E1/LVANDERF/LOCALS%7E1/TEMP/nsmail.txt (426 Bytes)

7

Hi,

I am kind of novice in RT. Can someone please tell me how the query

builder works? When I give the arguments and click on search how does
it build the query and what all tables does it refer to??? Any kind of
insight on this is greatly appreciated.

Regards,

Uday

DISCLAIMER:“The information contained in this message and the attachments (if any) may be privileged and confidential and protected from disclosure. You are hereby notified that any unauthorized use, dissemination, distribution or copying of this communication, review, retransmission, or taking of any action based upon this information, by persons or entities other than the intended recipient, is strictly prohibited. If you are not the intended recipient or an employee or agent responsible for delivering this message, and have received this communication in error, please notify us immediately by replying to the message and kindly delete the original message, attachments, if any, and all its copies from your computer system. Thank you for your cooperation.”

8

I don’t think anybody would help you with that unless you clarify your
question. Query Builder is for searching tickets in a RT instance. You
can build arbitrary tree of conditions aggregated by AND or OR boolean
operators. You choose conditions, clarify them in input fields and add
them to the query using ‘Add…’ button. On the right you see the
current tree of conditions. You can move them around, toggle boolean
operators, delete some.

Conditions you can build can touch any table in the DB.On Mon, Apr 27, 2009 at 5:46 PM, Uday Dey Uday.Dey@sierraatlantic.com wrote:

Hi,

I am kind of novice in RT. Can someone please tell me how the query

builder works? When I give the arguments and click on search how does it
build the query and what all tables does it refer to??? Any kind of insight
on this is greatly appreciated.

Regards,

Uday

DISCLAIMER:“The information contained in this message and the attachments
(if any) may be privileged and confidential and protected from disclosure.
You are hereby notified that any unauthorized use, dissemination,
distribution or copying of this communication, review, retransmission, or
taking of any action based upon this information, by persons or entities
other than the intended recipient, is strictly prohibited. If you are not
the intended recipient or an employee or agent responsible for delivering
this message, and have received this communication in error, please notify
us immediately by replying to the message and kindly delete the original
message, attachments, if any, and all its copies from your computer system.
Thank you for your cooperation.”

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.